-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Move containerd config from cloudup to nodeup #11986
Conversation
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.
Other than this, looks good to me.
pkg/apis/nodeup/config.go
Outdated
@@ -72,7 +72,7 @@ type Config struct { | |||
// Hooks are for custom actions, for example on first installation. | |||
Hooks [][]kops.HookSpec | |||
// ContainerdConfig config holds the configuration for containerd | |||
ContainerdConfig string `json:"containerdConfig,omitempty"` | |||
ContainerdOverrideConfig *string `json:"containerdConfig,omitempty"` |
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.
I want to add ContainerdConfigBase
so that people can merge some custom config with what kOps builds.
ContainerdOverrideConfig *string `json:"containerdConfig,omitempty"` | |
ContainerdConfigOverride *string `json:"containerdConfigOverride,omitempty"` |
nodeup/pkg/model/containerd.go
Outdated
if fi.StringValue(containerd.ConfigOverride) != "" { | ||
return *cluster.Spec.Containerd.ConfigOverride | ||
} |
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.
if fi.StringValue(containerd.ConfigOverride) != "" { | |
return *cluster.Spec.Containerd.ConfigOverride | |
} |
nodeup/pkg/model/containerd.go
Outdated
return "" | ||
} | ||
|
||
containerd := cluster.Spec.Containerd |
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 better to pass necessary values, such as RegistryMirrors
, in the NodeupConfig
than refer to the cluster spec. I'm trying to remove references to the cluster spec from nodeup as changes to cluster spec don't mark nodes as NeedUpdate.
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.
I just passed in the entire struct. All of them should trigger NeedUpdate.
d90f08d
to
7e6d7aa
Compare
7e6d7aa
to
c5d3360
Compare
nodeup/pkg/model/tests/containerdbuilder/from_docker_19.03.11/tasks.yaml
Outdated
Show resolved
Hide resolved
c5d3360
to
9897169
Compare
9897169
to
c17ec3a
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.
This should unblock GPU and other CRI related changes.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
|
Prepare for appending nvidia runtime configuration to containerd + potential support for registry authentication as secrets.