ArgoCD : add Rancher clusters to integrate the GitOps approach!

Search for a command to run...

No comments yet. Be the first to comment.
Summary Based on the Cloud Adoption Framework (CAF) and Well-Architected Framework (WAF), this project automates the audit of an entire Azure tenant in minutes, using AI and a sovereign environment to

Summary The N1 agent transforms how DevOps teams interact with Kubernetes infrastructures by combining conversational prompts and advanced automation, all powered by artificial intelligence. Concretel

We had the opportunity to attend Kubernetes Community Days (KCD) Suisse Romande, held at CERN in Geneva, on December 4th and 5th. These two days were full of discussions, workshops (we had the opportunity to participate to the Exoscale capture the fl...

With the recent annoncements regarding the Gateway APIs and the end of the Ingress Nginx maintenance, some aspects (historically managed by the Ingress Nginx) need to be re-adapted, we’ll shre one of those today: the TLS certificates management throu...

The CNCF has recently announced a major transition: Ingress Nginx, the “de facto” considered ingress controller, will officially reach end-of-life in March 2026. Official source here : https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/#:...

After sturggling with numbers of troubles trying to add a new Rancher cluster on ArgoCD, we wanted to give you our way to do it in few seconds without any worry !
First, you need to create a user in Rancher ('user and authentication' menu > create new user) and give him the standard user role in the Rancher cluster.

Now, you need to add the 'cluster owner' role to this new user on the cluster you would like to add. Go to the cluster parameters > cluster and project members.

Then add the correct right

When it's done, you can create the bearer token for this new user . First disconnect from Rancher and connect to the web interface with the newly created user.
Then, click on the user icon on the top right of the page and go to "Account & API keys"

Now, create the api key that ArgoCD will use to deploy resources on the cluster through the user.

Then, connect to your Rancher web interface and get the kubeconfig file of your "destination" cluster (the one you would like to add in ArgoCD).

When you have the file, get the following info from it :
caData : the certificate authority used to connect to your cluter
cluster: the URL to connect to the cluster
Now, we need to add a secret in our argoCD namespace and add the token, tls configuration and URL of the server, previously taken from the Kubeconfig file.
kind: Secret
data:
# Within Kubernetes these fields are actually encoded in Base64; they are decoded here for convenience.
# (They are likewise decoded when passed as parameters by the Cluster generator)
config: "{'bearerToken':{'token-xxxxxx'},
'tlsClientConfig':{'insecure':'false',
'caData':'xxxxxxx'}}"
name: "your-newcluster"
server: "https://yourrancherdomain.com/k8s/clusters/c-m-xxxxxxxx"
metadata:
labels:
argocd.argoproj.io/secret-type: cluster
Add this secret and go on your argoCD interface and you'll see that your cluster was added ! You can now start to synchronize Git / helm charts on it!
