-
Notifications
You must be signed in to change notification settings - Fork 182
Make k3s installer stages completely generic to the packaging system #17
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
Labels
enhancement ✨
New feature or request
Comments
@jeff-mccoy is this what you are calling "k8s native apply" or something else? |
That will block this, but the code and work are still independent. This has to do with cluster init. |
5 tasks
@jeff-mccoy will #237 close this? |
@jeff-mccoy will this be resolved when #237 merges? |
Yes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Removing all hard-coded elements of K3s will enable transparent support for alternative cluster technologies including K3d to make development and testing simpler. This will likely require #23 to be implemented.
Migrated from https://repo1.dso.mil/platform-one/big-bang/apps/product-tools/zarf/-/issues/31
The text was updated successfully, but these errors were encountered: