-
Notifications
You must be signed in to change notification settings - Fork 41.4k
Add explanation for kubeClient != nil in NewMainKubelet #97932
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
Add explanation for kubeClient != nil in NewMainKubelet #97932
Conversation
/sig node |
/cc @troy0820 |
|
||
var serviceLister corelisters.ServiceLister | ||
var serviceHasSynced cache.InformerSynced | ||
// If kubeClient == nil, we are running in standalone mode (i.e. no API servers) |
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.
good one :)
/approve |
Thanks @dims! |
Thanks for this. It was confusing me as well. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, ehashman, mrunalp, pacoxu, troy0820 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 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds an explanation for why we check for
kubeClient != nil
inNewMainKubelet
and hence why behaviour is different in each case.Which issue(s) this PR fixes:
N/A, this was a thing I was confused about and had to ask a question, and would like to document it for future contributors :)
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: