From b8bf7c3a6631666d59b309cc3a7a59246f66a0c8 Mon Sep 17 00:00:00 2001 From: Pavan Date: Tue, 5 Sep 2023 11:40:46 +0200 Subject: [PATCH] [Misc] CAP Operator: website image path updated Point to the right image path based on the public url. Change-Id: I2e5a21d513d0dc7eddfffa3697a113b6f7eaa015 --- website/content/en/docs/_index.md | 2 +- website/content/en/docs/concepts/operator-components/_index.md | 2 +- .../content/en/docs/concepts/operator-components/controller.md | 2 +- .../en/docs/concepts/operator-components/subscription-server.md | 2 +- website/content/en/docs/usage/tenant-provisioning.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/en/docs/_index.md b/website/content/en/docs/_index.md index 4e8c88d..82c0c0d 100644 --- a/website/content/en/docs/_index.md +++ b/website/content/en/docs/_index.md @@ -20,6 +20,6 @@ Main features of the CAP Operator: The following picture provides an overview of the major automation steps handled by the Operator during application deployment. -![workflow](/img/workflow.png) +![workflow](/cap-operator/img/workflow.png) Explore the following chapters to learn more. diff --git a/website/content/en/docs/concepts/operator-components/_index.md b/website/content/en/docs/concepts/operator-components/_index.md index 39b1747..68d22cd 100644 --- a/website/content/en/docs/concepts/operator-components/_index.md +++ b/website/content/en/docs/concepts/operator-components/_index.md @@ -18,6 +18,6 @@ The CAP Operator is comprised of the following components The following diagram depicts how the main components interact when deployed to a cluster. -![cluster-components](/img/block-cluster.png) +![cluster-components](/cap-operator/img/block-cluster.png) The following pages provide further details about the CAP Operator components. diff --git a/website/content/en/docs/concepts/operator-components/controller.md b/website/content/en/docs/concepts/operator-components/controller.md index 61faac0..008063b 100644 --- a/website/content/en/docs/concepts/operator-components/controller.md +++ b/website/content/en/docs/concepts/operator-components/controller.md @@ -20,4 +20,4 @@ The following _namespaced_ Custom Resources have been defined to be reconciled b > Parent-child relationships between custom resources are established by defining owner references for the children. -![controller](/img/block-controller.png) +![controller](/cap-operator/img/block-controller.png) diff --git a/website/content/en/docs/concepts/operator-components/subscription-server.md b/website/content/en/docs/concepts/operator-components/subscription-server.md index f5d42ef..3b4d5c1 100644 --- a/website/content/en/docs/concepts/operator-components/subscription-server.md +++ b/website/content/en/docs/concepts/operator-components/subscription-server.md @@ -18,7 +18,7 @@ The subscription server returns an `Accepted` (202) response code and starts a r Once the tenant provisioning process has completed (or has failed), the tracking routine will return the appropriate status to the SaaS Registry via an asynchronous callback (by obtaining the necessary authorization token). -![subscription](/img/block-subscription.png) +![subscription](/cap-operator/img/block-subscription.png) ([More details about asynchronous tenant subscription](https://controlcenter.ondemand.com/index.html#/knowledge_center/articles/2316430f7d804820934910db736cefbf).) diff --git a/website/content/en/docs/usage/tenant-provisioning.md b/website/content/en/docs/usage/tenant-provisioning.md index 7ad8299..79b0b4c 100644 --- a/website/content/en/docs/usage/tenant-provisioning.md +++ b/website/content/en/docs/usage/tenant-provisioning.md @@ -56,7 +56,7 @@ The `CAPTenant` reaches a Ready state, only after - Successful completion of all `CAPTenantOperation` steps - Creation of Istio `VirtualService` which allows HTTP requests on the tenant subdomain to reach the application -![tenant-provisioning](/img/activity-tenantprovisioning.png) +![tenant-provisioning](/cap-operator/img/activity-tenantprovisioning.png) ## Tenant Deprovisioning