[Feature] Support that was promised for enabling Beta APIs in Kubernetes v1.30 and higher

[tspearconquest]

Is your feature request related to a problem? Please describe.
In many AKS releases earlier this year it was noted that the K8s 1.30 release would mark the end of Beta APIs being enabled by default on AKS, and that a new flag would be provided "closer to the 1.30 release" to enable beta APIs.

This flag seems to have fallen off the roadmap, as it was not mentioned since the release at the end of June, and 1.30 was made GA at the end of July with no mention of this flag.

I am looking to enable beta APIs to get a feature that K8s 1.31 supports, but seem to be unable to do so despite the many months of promises of this flag coming.

Describe the solution you'd like
Microsoft to make good on the promise to give users a flag to enable beta APIs.

Describe alternatives you've considered
There are no alternatives other than building my own K8s cluster and managing the control plane myself, which I want to avoid.

Additional context
I'd love if the team could share some additional context on what happened here.

[grzesuav]

@tspearconquest what do you mean by beta api ? In regards to Features, all beta features are enabled - https://learn.microsoft.com/en-us/azure/aks/support-policies#unsupported-alpha-and-beta-kubernetes-features

AKS only supports stable and beta features within the upstream Kubernetes project. Unless otherwise documented, AKS doesn't support any alpha feature that is available in the upstream Kubernetes project.

I have been using them a lot in the past, however currently encounter on e weir behaviour which I reported.

[tspearconquest]

Hi Grzegorz, Take a look at the AKS release notes here: https://github.com/Azure/AKS/releases/tag/2024-06-09 The very first bullet point: "Starting 1.30 Kubernetes version and 1.27 LTS versions, beta apis will be disabled by default, when you upgrade to them. There will be an option provided to explicitly enable beta apis closer to the 1.30 release." This option never materialized and 1.30 was released back at the end of June. I'm looking to make use of a feature which graduated to beta in K8s 1.31 which allows using `matchLabelKeys` in pod anti affinity. This was an alpha feature in 1.30. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#matchlabelkeys

[tspearconquest]

I should clarify that I am running AKS with K8s 1.31, not the LTS 1.30 release -- I upgraded to 1.31 already.

[tspearconquest]

I just applied a manifest to my cluster with the matchLabelKeys field in the podAntiAffinity field. The matchLabelKeys field is not showing up in the yaml output when I request it back from the API. I don't get any error when applying the manifest so I cannot say for certain that the feature is disabled or what is going on, and would appreciate more insight from AKS regarding this.

[olsenme]

Are there any current or foreseeable specific beta API asks?

[tspearconquest]

Hi @olsenme not sure if you're asking me but yes; the one I listed in my last comment. Here's the link to the beta announcement for Kubernetes 1.31: https://kubernetes.io/blog/2024/08/16/matchlabelkeys-podaffinity/

This key seems to be accepted by the API but it's not showing up in the yaml output when I request the yaml back from the API server with kubectl get pod <podname> -o yaml

[microsoft-github-policy-service]

Action required from @aritraghosh, @julia-yin, @AllenWen-at-Azure

[microsoft-github-policy-service]

Issue needing attention of @Azure/aks-leads

[microsoft-github-policy-service]

Issue needing attention of @Azure/aks-leads