github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix discovery cache TTL to 6 hours

Browse Source 
Signed-off-by: Kazuki Suda <kazuki.suda@gmail.com>
This commit is contained in:
Kazuki Suda 2022-05-09 12:22:43 +09:00
parent bf52c1fd46
commit d2b4c017c8
No known key found for this signature in database
GPG Key ID: F735607417C95F32
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
staging/src/k8s.io/kubectl/pkg/cmd/delete/delete.go
View File

@ -72,8 +72,8 @@ var (
rest of the resource.
After a CustomResourceDefinition is deleted, invalidation of discovery cache may take up
to 10 minutes. If you don't want to wait, you might want to run "kubectl api-resources"
to refresh the discovery cache.`))
to 6 hours. If you don't want to wait, you might want to run "kubectl api-resources" to refresh
the discovery cache.`))
deleteExample = templates.Examples(i18n.T(`
# Delete a pod using the type and name specified in pod.json

2
test/cmd/discovery.sh
View File

@ -110,7 +110,7 @@ run_crd_deletion_recreation_tests() {
output_message=$(kubectl delete -f hack/testdata/CRD/example-crd-1-cluster-scoped.yaml)
kube::test::if_has_string "${output_message}" 'deleted'
# Invalidate local cache because cluster scoped CRD in cache is stale.
# Invalidation of cache may take up to 10 minutes and we are manually
# Invalidation of cache may take up to 6 hours and we are manually
# invalidate cache and expect that scope changed CRD should be created without problem.
kubectl api-resources
output_message=$(kubectl apply -f hack/testdata/CRD/example-crd-1-namespaced.yaml)