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

No SLES provision for servers or agents #94

Open
jonchines opened this issue Oct 13, 2023 · 1 comment
Open

No SLES provision for servers or agents #94

jonchines opened this issue Oct 13, 2023 · 1 comment

Comments

@jonchines
Copy link

It is a bit of an ironic omission that SuSE OS's are not covered in the context of this IaC. I have FIPS enabled SuSE 15sp5 AMI's in my account that I would like to use.

Side note, the RHEL, Ubuntu, etc. AMI's pulled in as data calls will build without FIPS (as far as I can tell) which may be of value for some to know/notice.

@adamacosta
Copy link
Collaborator

I believe you mean in the download.sh, right? Currently, to handle this, you can disable the download stage in cloud-init (set the Terraform variable "download" to false) and provide an AMI that already has the rke2 and awscli packages installed. I'm not sure if SLES 15 needs anything else (RHEL 9, which isn't yet supported by rke2, needs conntrack, socat, container-selinux, and iptables-nft).

For some context, these modules were originally created for our use on Platform One in a GovCloud environment that didn't have SLES AMIs available or approved for use and were created well before SuSE's acquisition of Rancher. Agreed we should be able to detect SLES and handle it at this point, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants