-
Notifications
You must be signed in to change notification settings - Fork 9
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
treewide: prepare separation of node installers #603
Conversation
277f877
to
ebdbf1a
Compare
This migrates the runtime-class-files to the new directory structure, as they only contain Microsoft-specific components and thus should not live in the shared space.
ebdbf1a
to
53a71bf
Compare
This also pulls out the node installer image to the new directory structure, as it also only holds Microsoft-specific components. A future refactoring should make this share the lowest layer (i.e. the node installer binary itself) between flavour-specific node installers.
53a71bf
to
07b653f
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.
Commit title should not end with a dot.
@@ -48,7 +48,7 @@ jobs: | |||
just get-credentials | |||
- name: Build and prepare deployments | |||
run: | | |||
just node-installer | |||
just microsoft-node-installer |
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.
please change to node-installer-microsoft, which is more intuitive for tab completion.
@@ -42,12 +42,12 @@ func NodeInstaller(namespace string) *NodeInstallerConfig { | |||
). | |||
WithTemplate(PodTemplateSpec(). | |||
WithLabels(map[string]string{"app.kubernetes.io/name": name}). | |||
WithAnnotations(map[string]string{"contrast.edgeless.systems/pod-role": "contrast-node-installer"}). | |||
WithAnnotations(map[string]string{"contrast.edgeless.systems/pod-role": "contrast-node-installer-microsoft"}). |
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.
Why do we need to change this?
Closing in favor of #611 |
To support multiple deployment "flavours" (i.e. AKS and bare-metal QEMU on TDX), we need to provide separate node installer deployments, as both deployment scenarios require different components to be installed on the hosts. This prepares this separation, by moving the Microsoft-specific runtime-class-files into the
microsoft
package set, and including the "flavour" of the deployment in the node installer image name.