karmada/docs/upgrading/v1.1-v1.2.md

54 lines
1.5 KiB
Markdown

# v1.1 to v1.2
Follow the [Regular Upgrading Process](./README.md).
## Upgrading Notable Changes
### karmada-controller-manager
The `hpa` controller has been disabled by default now, if you are using this controller, please enable it as per [Configure Karmada controllers](https://github.com/karmada-io/karmada/blob/master/docs/userguide/configure-controllers.md#configure-karmada-controllers).
### karmada-aggregated-apiserver
The deprecated flags `--karmada-config` and `--master` in v1.1 have been removed from the codebase.
Please remember to remove the flags `--karmada-config` and `--master` in the `karmada-aggregated-apiserver` deployment yaml.
### karmadactl
We enable `karmadactl promote` command to support AA. For details info, please refer to [1795](https://github.com/karmada-io/karmada/pull/1795).
In order to use AA by default, need to deploy some RBAC by following manifests.
<details>
<summary>unfold me to see the yaml</summary>
```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cluster-proxy-admin
rules:
- apiGroups:
- 'cluster.karmada.io'
resources:
- clusters/proxy
verbs:
- '*'
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: cluster-proxy-admin
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-proxy-admin
subjects:
- kind: User
name: "system:admin"
```
</details>
Please refer to [v1.2.0 Release Notes](https://github.com/karmada-io/karmada/releases/tag/v1.2.0) for more details.