Skip to content

Commit

Permalink
Update links in local-cluster.md
Browse files Browse the repository at this point in the history
  • Loading branch information
anirudhprasad-sap authored Oct 29, 2024
1 parent 272c7b1 commit 00c7703
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions content/en/docs/installation/local-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,19 +12,19 @@ description: >
To install the latest version of CAP Operator Manager, please execute the following command:

```bash
kubectl apply -f https://github.com/SAP/cap-operator-lifecycle/releases/download/manager%2Fv0.0.1/manager_manifest.yaml
kubectl apply -f https://github.com/SAP/cap-operator-lifecycle/releases/latest/download/manager_manifest.yaml
```

This would create namespace `cap-operator-system` with CAP Operator Manager installed.
This would create a namespace `cap-operator-system` with CAP Operator Manager installed.

![cap-op-man-install](/cap-operator-lifecycle/img/cap-op-man-install.png)
## Install CAP Operator using CAP Operator Manager
Once the CAP Operator Manager is running, you can install CAP operator by executing the following command:
Once the CAP Operator Manager is running, you can install the CAP operator by executing the following command:

```bash
kubectl apply -n cap-operator-system -f https://github.com/SAP/cap-operator-lifecycle/releases/download/manager%2Fv0.0.1/manager_default_CR.yaml
kubectl apply -n cap-operator-system -f https://github.com/SAP/cap-operator-lifecycle/releases/latest/download/manager_default_CR.yaml
```
**This would work only if the `ingressGatewayLabels` in your clusters matches the following values:**
**This would work only if the `ingressGatewayLabels` in your clusters match the following values:**

```yaml
ingressGatewayLabels:
Expand All @@ -34,7 +34,7 @@ kubectl apply -n cap-operator-system -f https://github.com/SAP/cap-operator-life
value: istio-ingressgateway
```
If not, you will have to manually create the `CAPOperator` resource by applying below yaml to `cap-operator-system` namespace after filling the `ingressGatewayLabels` values from your cluster.
If not, you must manually create the `CAPOperator` resource by applying the below yaml to the `cap-operator-system` namespace after filling in the `ingressGatewayLabels` values from your cluster.

```yaml
apiVersion: operator.sme.sap.com/v1alpha1
Expand All @@ -50,10 +50,10 @@ spec:
- name: <<--Label Name-->>
value: <<--Label Value-->>
```
Once the `CAPOperator` resource is created, the CAP Operator Manager will start installing the CAP Operator in the namespace. Once the resource is ready, you will be able to see the CAP Operator Pods running in the namespace.
Once the `CAPOperator` resource is created, the CAP Operator Manager will start installing the CAP Operator in the namespace. Once the resource is ready, you can see the CAP Operator Pods running in the namespace.

![cap-op-man-cr-ready](/cap-operator-lifecycle/img/cap-op-man-cr-ready.png)

CAP Operator Pods:

![cap-op-pods](/cap-operator-lifecycle/img/cap-op-pods.png)
![cap-op-pods](/cap-operator-lifecycle/img/cap-op-pods.png)

0 comments on commit 00c7703

Please sign in to comment.