-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Fix providerless kubelet startup #93607
Conversation
/lgtm |
node e2e flake on cpu resources
/retest |
@@ -84,9 +84,7 @@ func addCredentialProviderFlags(fs *pflag.FlagSet) { | |||
global := pflag.CommandLine |
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.
nit: no need to get global here and pass to addLegacyCloudProviderCredentialProviderFlags
. It can be taken when needed.
/retest |
c57adf5
to
93e2868
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
oops, pushed a commit meant for #93605 ... fixed |
/lgtm |
/retest |
2 similar comments
/retest |
/retest |
hmm |
verify is failing on #93623, wait until that is resolved to retest /hold |
/retest |
I'm not sure why the AKS e2es would start failing since they shouldn't use providerless builds but ran into this issue in another PR and this seems possibly related 🤔
|
that tag is not set by default so they'd have to be opting into it somehow it also doesn't relate to how credentials are parsed, only how a flag is registered (and only if the tag is set). |
@andrewsykim that log message is from kubetest, not kubelet:
|
kubernetes/test-infra#17869 bumped a bunch of dependencies including some azure related stuff, and some later PR caused us to actually upgrade to a new image containing these in kubetest. https://github.com/kubernetes/test-infra/commits/master/kubetest |
Ah, thanks for clarifying @BenTheElder! @andyzhangx @feiskyer can you look at this failure when you get a chance please? |
Thanks @BenTheElder @andrewsykim. The error is |
Nobody would have changed the credential without being asked to. |
@BenTheElder no worries, the credential issues have been fixed by test-infra-oncall. |
Circling back, if anyone's curious this was the issue: kubernetes/test-infra#18618 (comment) basically the format was invalid but the older go-toml version allowed it. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Follow up from #93579
That PR made the registration of the azure flags conditional (excluded in providerless builds), but the kubelet assumed the flag would be available when registering credential provider flags.
Does this PR introduce a user-facing change?:
/cc @BenTheElder @aojea