sks: add commands to generate karpenter-related manifests - #905
Merged
Conversation
Contributor
|
i'd call it generate-karpenter-manifests |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add a new
generate-karpenter-manifestscommand in thecompute/skscontext.It generates the kubernetes resources needed to enable Karpenter on a given cluster.
The code is displayed on the standard output.
Two flags allow to further tweak the command behavior:
--nodepool(-n): only display theNodePoolresource--exoscale-nodeclass(-e): only display theExoscaleNodeClassresourceWhen no flags are given, both are assumed, thus both resources are displayed.
Checklist
(For exoscale contributors)
CHANGELOG.md)Testing
The command was extensively tried out on a preprod cluster.