-
Notifications
You must be signed in to change notification settings - Fork 314
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
[Feature Request] Alpha Clusters #2058
Comments
@Azure/aks-pm issue needs labels |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
Would be awesome to get support for this, looking specifically at the LoadBalancer with Mixed Protocol new feature already mentioned in #2193 |
Interested as well, following. |
Any updates? Ephemeral Containers would be nice, tbh. |
Looking forward to use |
For this you would need at least Containerd 1.5 which is coming only with AKS 1.22+ Clusters |
We are also interested in being able to use feature gates to enable alpha features. In our case it's HostProcess container support on k8s 1.22 . Would be very convenient to have way of enabling alpha features. |
Looking forward to have support for this, we need this to enable mixed protocols in load balancers. |
same here, but i would like a solution where i have to specifically enable alpha feature gates instead of have all enabled. |
i agree enabling all of them is way too much compare to selectively enabling individual ones such as |
Agree, we also only need the LoadBalancer with mixed protocols feature. Wouldn't want to also enable every other alpha feature. |
I couldn't agree more about feature gates being desirable. For example, I'd like to be able to start development work on supporting ephemeral containers (https://kubernetes.io/docs/concepts/workloads/pods/ephemeral-containers/) before AKS rolls it out as a fully supported option. |
You can do this with AKS 1.23 which is public preview at the moment as |
Excellent, thankyou @philwelz . I incorrectly thought beta features were still gated off by default, but upon rechecking I can see I was mistaken. |
We would like to use StatefulSetStartOrdinal alpha feature gate on 1.26 |
@drzdbd1 Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@Shaybs Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@TilmanLacko-TomTom Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@yanrez Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@mehmettaskiner Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@philwelz Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@TacticalVilius Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@ringerc Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
@jamesongithub Is this still something you are interested in? Would like to learn more about your use case and why you are interested in this. |
|
back again, we got mixed protocol LB, but now we're interested in HPAContainerMetrics. this issue is really old at this point, it would be nice to either get some commentary from AKS about generally offering alpha-gated k8s features or simply be told "no" and have this issue closed. thanks! |
What are your thoughts if we were to support only latest stable version of AKS for alpha clusters? Would this meet your needs? |
If you're wanting to try out alpha features it seems you'd more likely want to test them on the latest preview cluster. |
This is something I am interested in as well. My microservices work in a choreography architecture, so I only need them to be on if there are work for them to do. Additionally, one of our workloads require 200gb of memory, so if 5 developers each have their own environment they reserve 1 Tb of memory just to have their helm chart deployed, but without having any actual workload. |
Anyone else thoughts on the proposal to support only on latest stable version? |
100% would meet our needs yes. we're happy to upgrade/roll-forward any time we need these things, also happy to flip a specific bit at cluster provisioning time and even totally rebuild our clusters to get features turned on. |
This would be fine for me, it shouldn't be an issue to keep our cluster updates to the latest version. |
@olsenme: this was added to the backlog on April 13 and then removed again completely on June 5. Does that mean that it's no longer planned? I'd like to add one more aspect: besides enabling feature gates, sometimes a feature also needs API groups enabled in the apiserver. Example (my current use case): https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#enabling-dynamic-resource-allocation |
CAPZ will support creating and joining alpha/beta worker nodes to AKS control plane. For more information see this PR and recorded demo from the community meeting. |
Support for sandbox clusters with all feature gates open to allow for testing of new k8s features before they become supported.
The text was updated successfully, but these errors were encountered: