-
Notifications
You must be signed in to change notification settings - Fork 980
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
Helm - Add NodePool and EC2NodeClass #5135
Comments
We had a similar request here: #1956. We are generally recommending that users build a "top-level chart" that take this chart as a dependency elsewhere since we are generally trying to avoid the burden of having to maintain the chart ourselves. given the number of options that we would have to support. |
hum... #1956 (comment), this commentary really makes sense. closing. |
@mtavaresmedeiros In my production cluster, I am using my own karpenter-nodepool chart, integrated into the karpenter chart as a child chart. Subchart dependencies declared in the # charts/karpenter/Chart.yaml
dependencies:
- name: karpenter-nodepool
version: 0.0.7
repository: "file://./charts/karpenter-nodepool"
condition: karpenter-nodepool.enabled Directory structure for karpenter # parent chart
├── Chart.lock
├── Chart.yaml
├── README.md
├── charts
│ └── karpenter-nodepool # subchart
├── crds
├── templates
└── values.yaml |
Description
What problem are you trying to solve?
Allow specifying NodePool and Ec2NodeClass
How important is this feature to you?
It will simplify the installation of the karpenter with helm, allowing specifying a node pool and ec2nodeclass in the initial installation.
Ex: Install the karpenter with the terraform in a Kubernetes cluster with fargate(serverless) or another option with 0 nodes, and install the GitOps tools after it, without the need to create another resource (NodePool and Ec2NodeClass), and has all things work out-of-the-box.
If it is fine, I can do the PR.
The text was updated successfully, but these errors were encountered: