Migrate PriorityLevelConfiguration from flowcontrol.apiserver.k8s.io/v1beta2

Kubernetes 1.29 removed PriorityLevelConfiguration v1beta2. The field that sets a level's share of the server, assuredConcurrencyShares, is called nominalConcurrencyShares in the newer versions, so the move is more than an apiVersion change.

The error

After the upgrade to 1.29, kubectl apply fails like this:

error: resource mapping not found for name: "<name>" namespace: "<ns>" from "<file>": no matches for kind "PriorityLevelConfiguration" in version "flowcontrol.apiserver.k8s.io/v1beta2"
ensure CRDs are installed first

What replaces it

Replacement: flowcontrol.apiserver.k8s.io/v1
Available since: 1.29
Deprecated in: 1.26
Removed in: 1.29

Check a manifest against 1.29, or read the official documentation.

Migration notes

The PriorityLevelConfiguration spec.limited.assuredConcurrencyShares field is renamed to spec.limited.nominalConcurrencyShares
The PriorityLevelConfiguration spec.limited.nominalConcurrencyShares field only defaults to 30 when unspecified, and an explicit value of 0 is not changed to 30.

Before and after

Before:

apiVersion: flowcontrol.apiserver.k8s.io/v1beta2
kind: PriorityLevelConfiguration
metadata:
  name: batch-jobs
spec:
  type: Limited
  limited:
    assuredConcurrencyShares: 10
    limitResponse:
      type: Reject

After:

apiVersion: flowcontrol.apiserver.k8s.io/v1
kind: PriorityLevelConfiguration
metadata:
  name: batch-jobs
spec:
  type: Limited
  limited:
    nominalConcurrencyShares: 10
    limitResponse:
      type: Reject

Helm upgrade fails after a cluster upgrade

If you installed this with Helm, helm upgrade can fail after the cluster is upgraded, even if the chart is already fixed. Which error appears depends on your Helm version and the error text:

Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "<name>" namespace: "<ns>" from "": no matches for kind "PriorityLevelConfiguration" in version "flowcontrol.apiserver.k8s.io/v1beta2"

Error: UPGRADE FAILED: current release manifest contains removed kubernetes api(s) for this kubernetes version and it is therefore unable to build the kubernetes objects for performing the diff. error from kubernetes: unable to recognize "": no matches for kind "PriorityLevelConfiguration" in version "flowcontrol.apiserver.k8s.io/v1beta2"

Helm compares your chart with the manifest stored with the release. That stored manifest still has the old API, and the cluster can no longer read it.

To check, get the stored manifest, and paste the output into the checker:

helm get manifest <release> -n <namespace>

To fix the stored record, use the helm-mapkubeapis plugin, latest tag v0.6.1. Try --dry-run first. Its README lists support for Helm v3, so check that it suits your Helm version.

helm plugin install https://github.com/helm/helm-mapkubeapis --version v0.6.1
helm mapkubeapis <release> --namespace <namespace> --dry-run

Helm's advice is to move releases to supported APIs before you upgrade the cluster, and not to roll back to a release from before that change.