> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/setup/deploymentnew/getting-started/production/rancher.md).

# Administration Using Rancher

## Cluster administration

In V3 installation cluster can be administered by logging into organisation wide [Rancher setup](https://github.com/mosip/k8s-infra/tree/main/rancher). Rancher is integrated with Keycloak for authentication. To provide cluster access to a user perform the following steps as administrator:

1. Login into organisation wide Keycloak e.g `https://iam.xyz.net`. It is assumed that you have `admin` role in Keycloak.
2. Create a new user.
3. Make sure a strong password is set for the same under *Credentials* tab.
4. On *Details* tab you should see *Update Password* flag under *Required User Actions*. This will prompt a user to change the password during first login. Disable the same only if you are sure you don't want user to change password.

   ![](https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-7f426dd20014149e509bc5f0c839c56ffe5a808e%2Fkeycloak-user-create.png?alt=media\&token=467b6060-a145-4043-94de-810c62eb9c4d)
5. Login to Rancher as administrator, e.g. `https://rancher.xyz.net`.
6. Select a cluster for which you would like to enable access to the user.
7. Add the user as member of the cluster.
8. Assign a role, e.g Cluster Owner, Cluster Viewer.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mosip.io/1.2.0/setup/deploymentnew/getting-started/production/rancher.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.