mirror of
https://github.com/confidential-containers/confidential-containers.git
synced 2025-10-22 07:52:15 +00:00
quickstart: update operator installation steps (#73)
The operator dropped the deploy/deploy.yaml based deployment and moved to a kustomize based one so update the docs to reflect that change. Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
This commit is contained in:
@@ -59,14 +59,22 @@ for development purposes.
|
|||||||
- Ensure at least one Kubernetes node in the cluster is having the label `node-role.kubernetes.io/worker=`
|
- Ensure at least one Kubernetes node in the cluster is having the label `node-role.kubernetes.io/worker=`
|
||||||
|
|
||||||
|
|
||||||
For more details on the operator, including the custom resources managed by the operator, refer to the operator [docs](https://github.com/confidential-containers/operator)
|
For more details on the operator, including the custom resources managed by the operator, refer to the operator [docs](https://github.com/confidential-containers/operator).
|
||||||
|
|
||||||
## Operator Installation
|
## Operator Installation
|
||||||
|
|
||||||
### Deploy the the operator
|
### Deploy the the operator
|
||||||
|
|
||||||
|
Deploy the operator by running the following command where `<RELEASE_VERSION>` needs to be substituted
|
||||||
|
with the desired [release tag](https://github.com/confidential-containers/operator/tags).
|
||||||
|
|
||||||
```
|
```
|
||||||
kubectl apply -f https://raw.githubusercontent.com/confidential-containers/operator/main/deploy/deploy.yaml
|
kubectl apply -k github.com/confidential-containers/operator/config/release?ref=<RELEASE_VERSION>
|
||||||
|
```
|
||||||
|
|
||||||
|
For example, to deploy the `v0.2.0` release run:
|
||||||
|
```
|
||||||
|
kubectl apply -k github.com/confidential-containers/operator/config/release?ref=v0.2.0
|
||||||
```
|
```
|
||||||
|
|
||||||
Wait until each pod has the STATUS of Running.
|
Wait until each pod has the STATUS of Running.
|
||||||
|
Reference in New Issue
Block a user