# KOTS: How to pin kotsadm to a specific version
**URL:** https://community.replicated.com/t/kots-how-to-pin-kotsadm-to-a-specific-version/571
**Category:** Supporting your customers
**Tags:** version, kots, support
**Created:** [September 14, 2021, 2:00pm UTC](https://community.replicated.com/t/kots-how-to-pin-kotsadm-to-a-specific-version/571 "2021-09-14T14:00:48Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@AJ-Jester](https://community.replicated.com/u/AJ-Jester)
#### Post date: [September 14, 2021, 2:00pm UTC](https://community.replicated.com/t/kots-how-to-pin-kotsadm-to-a-specific-version/571/1 "2021-09-14T14:00:48Z")
How do we go about pinning KOTS Adm to a specific version?
---
### Author:  [@AJ-Jester](https://community.replicated.com/u/AJ-Jester)
#### Post date: [September 14, 2021, 2:01pm UTC](https://community.replicated.com/t/kots-how-to-pin-kotsadm-to-a-specific-version/571/2 "2021-09-14T14:01:03Z")
Depending on whether its an Embedded or Existing cluster, its as follows:
# Embedded
- In the kURL Installer yaml spec, you need to specify the version you want to pin it to.
```auto
apiVersion: "cluster.kurl.sh/v1beta1"
kind: "Installer"
metadata:
name: "latest"
spec:
kotsadm:
version: "1.50.0"
```
- Rerun kURL installer you ran during the initial install.
# Existing
1. Download a specific version from here [Releases · replicatedhq/kots · GitHub](https://github.com/replicatedhq/kots/releases)
2. Untar it, should be a single binary.
3. Move it to `/usr/local/bin/kubectl-kots`, `chmod +x` if needed.
4. Confirm with `kubectl kots version`.
5. Run `kubectl kots admin-console upgrade -n `.
**Note:** The KOTS binary locally on your workstation (where `kubectl` is run) must be updated first before running the command to upgrade kots admin console in existing clusters.