github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-23 11:50:44 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #109896 from superbrothers/kubectl-delete-fix-discovery-cache-ttl

Browse Source 
Fix discovery cache TTL to 6 hours
This commit is contained in:
Kubernetes Prow Robot 2022-05-10 14:33:36 -07:00 committed by GitHub
commit cf64022a0f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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)