> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Helm deployment prerequisites

> Helm deployment guidance now states component-specific Kubernetes API baselines.

<Badge stroke icon="calendar-days" iconType="regular">August 26, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams planning or operating Helm deployments for Access Manager, Lerian Console, Fetcher, or Tracer.

## What changed

***

The Helm guides now state component-specific Kubernetes API baselines: Console supports Kubernetes 1.20+, while Access Manager and the infrastructure guide require Kubernetes 1.23+ because their charts use `autoscaling/v2` and `policy/v1`. Helm 3.8+ remains required for OCI registry support.

The guides also clarify that only products and components with published charts use the documented Helm workflow. This is a documentation correction; it does not announce a runtime release.

## Impact

***

**Classification: Review recommended.** Existing and planned Helm deployments should use the correct baseline for each chart.

## What you need to do

***

<Steps>
  <Step>Confirm the Kubernetes version for each chart you deploy before installing or upgrading it.</Step>
  <Step>Use a currently supported Kubernetes minor release in production.</Step>
  <Step>Confirm that your target product or component has a published Helm chart before adopting the Helm workflow.</Step>
</Steps>

### Deadline

Review before the next Helm installation or upgrade.

## Resources

***

* [Helm at Lerian](/en/platform/deploy/helm-overview)
* [Access Manager via Helm](/en/platform/deploy/access-manager/access-manager-helm)
* [Infrastructure via Helm](/en/platform/deploy/infrastructure/infrastructure-helm)