Skip to content

docs: drop certificates.k8s.io/v1beta1 requirement from 1.x install guide - #578

Open
AllardQuek wants to merge 2 commits into
kagent-dev:mainfrom
AllardQuek:docs/remove-certificates-v1beta1-requirement
Open

AllardQuek wants to merge 2 commits into
kagent-dev:mainfrom
AllardQuek:docs/remove-certificates-v1beta1-requirement

Conversation

@AllardQuek

@AllardQuek AllardQuek commented Oct 10, 2026 •

Copy link
Copy Markdown

Summary

  • Removes the certificates.k8s.io/v1beta1 setup from step 3 of the kagent 1.x install guide. Kubernetes 1.37 serves PodCertificateRequest and ClusterTrustBundle at certificates.k8s.io/v1 by default.
  • kind: drops the runtimeConfig block; the command is now kind create cluster --name kagent --image kindest/node:v1.37.0.
  • Existing clusters: drops the kube-apiserver --runtime-config steps, notes that no API server change is needed (including managed control planes such as EKS, GKE, AKS), and verifies with kubectl api-resources --api-group=certificates.k8s.io.

Fixes kagent-dev/kagent#3083

Notes

  • Substrate still falls back to v1beta1 when v1 is absent, and its setup-gcp README treats 1.36 with beta APIs enabled as supported. This guide requires 1.37+, so the beta steps are removed rather than relabeled as 1.36-only. If 1.36 should stay documented, that would be a separate follow-up.
  • The Substrate chart text (README, NOTES.txt, values.yaml) in kagent-dev/substrate is out of scope here.

Test plan

  • hugo --minify (v0.160.0 extended) builds without errors
  • Rendered 1.x/setup/installation page shows the new step 3 and contains no v1beta1
  • Ran the guide's kind command (kindest/node:v1.37.0, kind v0.33.0, no runtimeConfig): kubectl api-versions | grep certificates.k8s.io shows only certificates.k8s.io/v1, and kubectl api-resources --api-group=certificates.k8s.io lists certificatesigningrequests, clustertrustbundles, and podcertificaterequests at v1. Substrate/kagent install not re-run.

Signed-off-by: Allard <AllardQuek@users.noreply.github.com>
…uide

Kubernetes 1.37 serves PodCertificateRequest and ClusterTrustBundle at
certificates.k8s.io/v1 by default, so the kind runtimeConfig and the
kube-apiserver --runtime-config steps are no longer needed.

Signed-off-by: Allard <AllardQuek@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOCS] Install guide and Substrate chart still require certificates.k8s.io/v1beta1, which 1.0.0-alpha8 does not need on Kubernetes 1.37

1 participant