> For the complete documentation index, see [llms.txt](https://docs.mechcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mechcloud.io/ai-agents/rest-agent/kubernetes/adding-a-system-account.md). # Adding a system account ### Deploy MechCloud Proxy for a REST API Deploy either MechCloud OIDC or HTTPs Proxy depending on your requirement. See [Broken mention](broken://pages/GERmvubzIEmU8Vfi68y9#choosing-between-mechcloud-oidc-and-https-proxies) for more details. ### Registering a system account in MechCloud Each system account registered in **MechCloud OIDC proxy** must have a unique id which is specified against **Credentials ID** while registering an account for the target system. * Login to MechCloud [console](https://portal.mechcloud.io). * Navigate to **Infrastructure -> System Accounts**. * Click on **New System Account** button. * Enter a name for the account. * Choose **Kubernetes** in the dropdown. * Enter the base url of Kubernetes API. * If you are using minikube and exposing its api using [MechCloud HTTPS Proxy](https://github.com/mechcloud/mechcloud-flask-proxy), then the base url of k8s api will be \*\*; * (Optional) If K8s api is running with a self-signed certificate, then open the base url (e.g. ) in the browser and accept the certificate warning so that MechCloud can communicate with the k8s api. * Click on **fetch version** link. If you are able to see k8s version, it means MechCloud is able to communicate with your k8s api. Otherwise, you can debug it with the help of browser devtools. * If the k8s api require authentication, then add an account for k8s api in this proxy. Finally, enter the value of id attribute, which you chose in **MechCloud OIDC Proxy**, against **Credentials ID.**
* If the api is not secured then toggle the **Secured API** button to off position.