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
Pre-pull cilium and kube-proxy in warming mode #11258
Conversation
7d8bcbe
to
26bb501
Compare
26bb501
to
202e440
Compare
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.
Addressing the warning log level is the only thing I would consider potentially blocking.
nodeup/pkg/model/kube_proxy.go
Outdated
Runtime: b.Cluster.Spec.ContainerRuntime, | ||
} | ||
c.AddTask(pullTask) | ||
} |
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.
It would be simpler to wrap this up in a receiver off of NodeupModelContext
. It would be even simpler still to push the ConfigurationMode
test down into the task (renaming it WarmImageTask
.)
a10c4ab
to
4a32e2d
Compare
@olemarkus what's your take on extracting out some of the boilerplate to common code? I suspect these aren't going to be the only two images we're going to want to warm-pull. |
4a32e2d
to
6850862
Compare
Something like this, perhaps? |
Something like that, modulo the compile error. |
Co-authored-by: John Gardiner Myers <jgmyers@proofpoint.com>
6850862
to
df4f429
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johngmyers 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 |
This PR will optimise Node initialisation time by pulling kube-proxy and cilium images if we are in warming mode.