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: Don't reuse the ignorePreflightErrors
from initCfg for reset
#113355
Conversation
…set` The init config file fetched from cluster won't have `ignorePreflightErrors` set, and shouldn't try to reuse it even it's set with any value. Instead, it should be defined in reset config file and fetch from it when the reset config is ready. Signed-off-by: Dave Chen <dave.chen@arm.com>
@chendave: 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. |
/release-note-none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chendave, neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The init config file fetched from cluster won't have
ignorePreflightErrors
set, and shouldn't try to reuse it even it's set with any value.Instead, it should be defined in reset config file and fetch from it when the reset config is ready.
Signed-off-by: Dave Chen dave.chen@arm.com
What type of PR is this?
/kind cleanup
For prepare of the reset config,
What this PR does / why we need it:
Which issue(s) this PR fixes:
Related: kubernetes/kubeadm#2489
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: