-
Notifications
You must be signed in to change notification settings - Fork 64
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
Change node autoscaler setup logic #6699
Labels
kind/enhancement
sig/api
Denotes a PR or issue as being assigned to SIG API.
sig/ui
Denotes a PR or issue as being assigned to SIG UI.
Milestone
Comments
Evaluate if it’s possible to convert node autoscaler addon into an application, which will solve the UI logic since an application can be managed during cluster creation time |
This parts need to be automated in a way that it's injected by KKP. |
csengerszabo
added
the
sig/app-management
Denotes a PR or issue as being assigned to SIG App Management.
label
Jul 3, 2024
|
csengerszabo
added
kind/enhancement
sig/api
Denotes a PR or issue as being assigned to SIG API.
labels
Jul 9, 2024
/milestone clear |
Requires kubermatic/kubermatic#13913 |
csengerszabo
removed
the
sig/app-management
Denotes a PR or issue as being assigned to SIG App Management.
label
Dec 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/enhancement
sig/api
Denotes a PR or issue as being assigned to SIG API.
sig/ui
Denotes a PR or issue as being assigned to SIG UI.
In step 4 of cluster creation at the Node Autoscaling part, there is a helper text saying:
Enable "cluster-austoscaler" addon to apply these changes
If the addon is needed, and since this step is before we can add any addons to the cluster, it’s not logical to set this here.
Instead:
Option 2 is preferred.
App management issue: kubermatic/kubermatic#13913
The text was updated successfully, but these errors were encountered: