Skip to content

add autopilot cluster integration tutorial #1413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vitalii-codefresh wants to merge 2 commits into
base: master
Choose a base branch
from
+8 −1
Open

add autopilot cluster integration tutorial #1413

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a17edf9
add autopilot cluster integration tutorial
vitalii-codefresh Mar 25, 2026
230d814
remove autopilot cluster integration tutorial
vitalii-codefresh Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion _docs/integrations/kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,6 @@ If this is your first time, you'll be prompted to authenticate using your Google

For GKE cluster versions >=1.19 basic authentication is deprecated. You can add the GKE cluster manually by [using the custom Kubernetes integration option](#adding-any-other-cluster-type-not-dependent-on-any-provider) instead.


### Adding an AKS cluster

To add an Azure cluster, select *Azure AKS* from the drop-down menu instead of *Azure AKS SP*. Click the *Authenticate button* and enter your Azure credentials. You will see a description of all permissions that Codefresh needs
Expand Down Expand Up @@ -392,6 +391,14 @@ echo $(kubectl get secret -n kube-system -o go-template='{{index .data "token" }
{% endraw %}
{% endhighlight %}

If you try to use GKE Autopilot clusters they have additional restrictions compared to standard GKE clusters. Specifically, **modifications to the `kube-system` namespace are not allowed** in Autopilot clusters. Therefore, you must use a custom namespace for the Codefresh service account.

{{site.data.callout.callout_warning}}
**IMPORTANT**
GKE Autopilot clusters do not allow modifications to the `kube-system` namespace. Use the dedicated namespace approach described below instead of the standard integration method.
REPLACE all occurrences in manifests and commands of "kube-system" on your own namespace for instance 'codefresh' or what you have.
{{site.data.callout.end}}

#### The proper/secure way Kubernetes 1.23 and older

For production environments you should create a service account and/or role for Codefresh access.
Expand Down