-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubeadm init --dry-run --upload cert fails in upload-certs phase with 'secret not found' #2649
Comments
@sj98ta: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@sj98ta: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/transfer kubeadm |
i haven't tested personally dry-run with upload-certs, but this is likely a matter of hooking the right dry-run client and make sure it has secrets...alternatively we can just exclude the API call to GET secrets when dry-running... can you please run this command with --v=5 and show the full output? |
Sure... Here you go.
|
What happened?
Executing the command
kubeadm init --dry-run --upload-certs
, the command fails withWhat did you expect to happen?
I would expect the dry run with upload-certs to have succeeded.
How can we reproduce it (as minimally and precisely as possible)?
Execute the command
kubeadm init --dry-run --upload-certs
Anything else we need to know?
No response
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: