-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Open
Labels
area/web-developmentIssues or PRs related to the kubernetes.io's infrastructure, design, or build processesIssues or PRs related to the kubernetes.io's infrastructure, design, or build processespriority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/docsCategorizes an issue or PR as relevant to SIG Docs.Categorizes an issue or PR as relevant to SIG Docs.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
In the example for "Bootstrap Token Secret Format", the value for expiration is several years old. This means that if you are testing with the example, it will appear to be created, but it is not actually created, since it was rejected because the expiration date was expired. Consider putting a later expiration date in the example or making a note about it in the paragraphs that follow. Otherwise, it is not incredibly obvious why the secret does not successfully create.
kubectl apply -f bootstrap-token-07401b.yaml
secret/bootstrap-token-07401b created
kubectl get secret -n kube-system
No resources found in kube-system namespace.
Version: v1.33.5
Metadata
Metadata
Assignees
Labels
area/web-developmentIssues or PRs related to the kubernetes.io's infrastructure, design, or build processesIssues or PRs related to the kubernetes.io's infrastructure, design, or build processespriority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.sig/docsCategorizes an issue or PR as relevant to SIG Docs.Categorizes an issue or PR as relevant to SIG Docs.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.