From 00c770376836048339e3ba6e521733333a47189f Mon Sep 17 00:00:00 2001 From: anirudhprasad-sap <126493692+anirudhprasad-sap@users.noreply.github.com> Date: Tue, 29 Oct 2024 10:22:43 +0100 Subject: [PATCH] Update links in local-cluster.md --- content/en/docs/installation/local-cluster.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/docs/installation/local-cluster.md b/content/en/docs/installation/local-cluster.md index cc189c0..799bd8d 100644 --- a/content/en/docs/installation/local-cluster.md +++ b/content/en/docs/installation/local-cluster.md @@ -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: @@ -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 @@ -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) \ No newline at end of file +![cap-op-pods](/cap-operator-lifecycle/img/cap-op-pods.png)