Quick clarification: do you mean the Helm chart for running Prefect workers on Kubernetes, or a chart to self-host the Prefect API/UI? For Prefect 2.x, most users only need the worker chart. - If you’re deploying workers: use the

prefect-worker

chart from the Prefect Helm repo. The latest chart is compatible with Prefect 2.x as long as you pin the container image to a 2.x tag (e.g.,

image.tag: 2-latest

or a specific 2.x patch). - Helm repo: prefect-helm - Docs (Prefect 2.x): Deploying workers to Kubernetes How to find the latest chart version that explicitly targets Prefect 2.x (appVersion 2.*): 1) Add and update the repo:

helm repo add prefect <https://prefecthq.github.io/prefect-helm>
helm repo update

2) List all versions:

helm search repo prefect/prefect-worker -l

3) Inspect a candidate version’s appVersion:

helm show chart prefect/prefect-worker --version <chart_version>

Pick the highest chart version where

appVersion

starts with

2.

. If you want, I can pull the exact version for you—just say the word. - If you’re looking to self-host the API/UI: the currently maintained

prefect-server

Helm chart targets Prefect 3.x. For Prefect 2.x, most users ran the API locally or used Prefect Cloud. If you specifically need a 2.x self-hosted setup, let me know your requirements and I’ll outline viable options.

Great — for Prefect 2.x workers on Kubernetes, use the Prefect Helm chart: - Chart name:

prefect/prefect-worker

- Helm repo: prefect-helm - Chart source/README: prefect-helm repo (prefect-worker) Key point for Prefect 2.x: it’s safe to use the latest

prefect-worker

chart; just pin the container image to a Prefect 2.x tag (e.g.,

2-latest

or a specific 2.x patch). The chart is compatible across Prefect versions via the image you choose. Quick start

helm repo add prefect <https://prefecthq.github.io/prefect-helm>
helm repo update

Create a secret with your API key (example name: prefect-api-key):

kubectl create secret generic prefect-api-key \
  --from-literal=PREFECT_API_KEY=<YOUR_API_KEY> \
  -n prefect

Install with a values file that pins Prefect 2.x (minimal example):

# values.yaml
image:
  repository: prefecthq/prefect
  tag: 2-latest
  pullPolicy: IfNotPresent

worker:
  workPool: my-k8s-pool
  tags: ["k8s", "prod"]

extraEnv:
  - name: PREFECT_API_URL
    value: <https://api.prefect.cloud/api/accounts/<account_id>/workspaces/<workspace_id>>

extraEnvFrom:
  - secretRef:
      name: prefect-api-key

Then:

helm install my-worker prefect/prefect-worker -n prefect -f values.yaml --create-namespace

If you specifically need “the latest chart version whose appVersion starts with 2.x” (instead of just using the latest chart and pinning the image), you can identify it locally with:

helm search repo prefect/prefect-worker -l
helm show chart prefect/prefect-worker --version <chart_version> | grep appVersion

If you’d like, I can pull and report the exact current chart version that lists an appVersion of 2.x.

Short answer: use prefecthq/prefect:2.17.1-python3.11 Details: - The latest Prefect 2.x release is 2.17.1, and the corresponding Python 3.11 image tag is: - prefecthq/prefect:2.17.1-python3.11 - There isn’t an official “-kubernetes” image suffix for Prefect 2.x. The same image is used in Kubernetes, so replace your current tag

2.16.6-python3.11-kubernetes

with

2.17.1-python3.11

. Examples:

docker pull prefecthq/prefect:2.17.1-python3.11

If you prefer a moving pointer within 2.x (not pinned), you can use: - prefecthq/prefect:2-python3.11 Note: pinning to an exact version is recommended for reproducibility. Refs: - Docker usage guide: Prefect 2.x Docker guide - Kubernetes deployments: Prefect 2.x Kubernetes guide If you need a different Python version or a conda-based image, let me know and I’ll share the exact tag.

Short answer: there isn’t a specific bitnami/common version tied to a Prefect image tag. The bitnami/common Helm library is independent of the Prefect Docker image (e.g., 2.17.0-python3.11[-kubernetes]). You should use the version required by your Helm chart, or otherwise the latest compatible 2.x for your Helm/Kubernetes versions. Recommendations: - If you’re using a published Helm chart: follow the dependency version in that chart’s Chart.yaml. Many charts pin a specific range for bitnami/common. - If this is your own/custom chart: it’s generally safe to bump to the latest 2.x bitnami/common that’s compatible with your Helm/K8s versions. The library chart doesn’t ship runtime resources, but do check the changelog for helper/template changes. How to check the latest available versions locally:

helm repo add bitnami <https://charts.bitnami.com/bitnami>
helm repo update
helm search repo bitnami/common --versions | head -n 10

Helpful links: - README: bitnami/common (README) - Changelog: bitnami/common (CHANGELOG) If you share: - the Helm chart you’re deploying (or its Chart.yaml), and - your Helm and Kubernetes versions, I can recommend an exact bitnami/common version and call out any breaking changes from your current 2.9.2.

Short answer: pick the latest 2.x of bitnami/common your Helm/K8s support. It’s independent of the Prefect image tag. Practical recommendation: - If you’re maintaining your own chart, set a semver range and let Helm resolve the latest 2.x:

dependencies:
  - name: common
    repository: <https://charts.bitnami.com/bitnami>
    version: ">=2.9.0 <3.0.0"

Then:

helm repo add bitnami <https://charts.bitnami.com/bitnami>
helm repo update
helm dependency update <your-chart>

- If you need a fixed pin: choose the highest 2.x currently available in the repo. You can discover it with:

helm search repo bitnami/common --versions | head -n 10

Pick the topmost 2.x and set that exact version in Chart.yaml. Notes: - Upgrading within 2.x should be safe; it’s a Helm library chart (templates/helpers only). Still, review the changelog for any helper changes that could affect your templates and test with:

helm template <your-chart> --debug > /dev/null

Refs: - bitnami/common README - bitnami/common CHANGELOG If you share your Helm and Kubernetes versions (and whether you’re using an upstream chart), I can suggest an exact version and call out anything noteworthy moving from 2.9.2.