Skip to content
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

Support CAPA/CAPZ/CAPG-ready SLE Micro images #1978

Open
anmazzotti opened this issue Feb 26, 2024 · 2 comments
Open

Support CAPA/CAPZ/CAPG-ready SLE Micro images #1978

anmazzotti opened this issue Feb 26, 2024 · 2 comments
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request

Comments

@anmazzotti
Copy link
Contributor

When using CAPA we are relying on AWS hosted images.
Normally, the images coming from the AWS marketplace should be enough.
Publishing a SLE Micro image there would solve the issue.

However, when working in airgap mode, the images need some custom baking to add some specific version of the k8s binaries, like rke2 for example.
This would require the user to bake custom images through the provider-specific image building/publishing tool.

The elemental-toolkit could be a provider agnostic (and recommended) way to bake these custom images.
This should mostly involve documentation, with a custom section on how to publish the images for consumption on each provider.

It can be extended to e2e test coverage, to make sure that elemental built images can be published to each supported provider and can be used to deploy a cluster, using rancher-turtles with the cluster-api-provider-rke2.

@anmazzotti anmazzotti added kind/documentation Improvements or additions to documentation kind/enhancement New feature or request labels Feb 26, 2024
@anmazzotti
Copy link
Contributor Author

anmazzotti commented Feb 27, 2024

For example, for CAPA this should translate to:

  1. Create a raw disk image using elemental-toolkit
  2. Push the image as raw object to a S3 bucket
  3. Import the disk as snapshot
  4. Create an AMI from the snapshot
  5. Reference the AMI when creating new CAPI AWSMachineTemplates

This can all be automated through CLI, so the first 4 steps could just be done periodically or on demand by a CI agent.

@anmazzotti
Copy link
Contributor Author

anmazzotti commented Feb 27, 2024

Similarly, for CAPG:

  1. Create a raw disk image using elemental-toolkit
  2. Import the raw image on GCP
  3. Reference the image when creating new CAPI GCPMachineTemplates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant