Fix the image ref structure

ArnobKumarSaha · ArnobKumarSaha · commit 288f7756ba8a · 2026-06-14T22:01:59.000+06:00
Signed-off-by: Arnob Kumar Saha &lt;arnob@appscode.com&gt;
diff --git a/docs/platform/guides/account-management/kubernetes/credentials.md b/docs/platform/guides/account-management/kubernetes/credentials.md
@@ -263,7 +263,7 @@ Details:
 
 Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from previous step.
 
-<img  width="50%" src="images/aws-cred.png">
+![Aws Cred](images/aws-cred.png)
 
 <!-- ![Add AWS Credential](../images/aws-cred.png) -->
 
@@ -284,7 +284,7 @@ The command will output a JSON response containing the service principal details
 Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 
-<img align="right" width="50%" src="images/do-cred.png">
+![Do Cred](images/do-cred.png)
 
 ## Digital Ocean
 To access Digital Ocean Managed clusters, you need to create a API token from Digital Ocean.
@@ -324,7 +324,7 @@ To access GKE clusters, you need to create a GCP service account with with conta
 
 Then add the service account credentials [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
-<img align="right" width="50%" src="images/gcp-oauth.png">
+![Gcp Oauth](images/gcp-oauth.png)
 
 ## Google OAuth
 
@@ -339,7 +339,7 @@ This will create a credential, you will be able to access your k8s cluster with.
 
 <br><br><br>
 
-<img align="right" width="50%" src="images/linode-cred.png">
+![Linode Cred](images/linode-cred.png)
 
 ## Linode
 
@@ -353,7 +353,7 @@ Then add the credential [here](https://appscode.com/id/{user}/user/settings/cred
 
 <br><br><br>
 
-<img align="right" width="50%" src="images/rancher-cred.png">
+![Rancher Cred](images/rancher-cred.png)
 
 ## Rancher
 
@@ -371,7 +371,7 @@ Copy the generated access key, secret key, and API endpoint from the `Account &
 
 Next, add these credentials to the [KubeDB Platform user settings credentials page](https://appscode.com/id/{user}/user/settings/credentials/create).
 
-<img align="right" width="50%" src="../images/credentials/azureStorage.png">
+![Azure Storage](../images/credentials/azureStorage.png)
 
 ## Azure Storage
 
@@ -384,7 +384,7 @@ Then add the credential [here](https://appscode.com/id/{user}/user/settings/cred
 
 <br><br><br><br>
 
-<img align="right" width="50%" src="../images/credentials/cloudflareStorage.png">
+![Cloudflare Storage](../images/credentials/cloudflareStorage.png)
 
 ## Cloudflare R2 Storage
 
@@ -397,7 +397,7 @@ Then add the credential [here](https://appscode.com/id/{user}/user/settings/cred
 
 <br><br><br><br>
 
-<img align="right" width="50%" src="../images/credentials/Hetzner.png">
+![Hetzner](../images/credentials/Hetzner.png)
 
 ## Hetzner
 
@@ -412,7 +412,7 @@ Then add the credential [here](https://appscode.com/id/{user}/user/settings/cred
 
 <br><br><br>
 
-<img align="right" width="50%" src="../images/credentials/Scaleway.png">
+![Scaleway](../images/credentials/Scaleway.png)
 
 ## Scaleway
 
@@ -427,7 +427,7 @@ Then add the credential [here](https://appscode.com/id/{user}/user/settings/cred
 
 <br><br><br>
 
-<img align="right" width="50%" src="../images/credentials/vultr.png">
+![Vultr](../images/credentials/vultr.png)
 
 ## Vultr
 
diff --git a/docs/platform/selfhost-setup/README.md b/docs/platform/selfhost-setup/README.md
@@ -19,7 +19,7 @@ Welcome to KubeDB Platform's Self-Hosted deployment! Whether you're looking for
 
 Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
 
-<img src="images/installer-home.png">
+![Installer Home](images/installer-home.png)
 <br/>
 <br/>
 Click on the `Create New Installer` button to get started. You can either choose deployment type `Self Hosted Demo` or `Self Hosted Production`. Provide the required data and click `Done` button to generate the installer. Upon generation of the installer, you will get the documentation how to host KubeDB Platform Server on your own.
diff --git a/docs/platform/selfhost-setup/install/aws-marketplace.md b/docs/platform/selfhost-setup/install/aws-marketplace.md
@@ -370,12 +370,12 @@ The expiry time for this installer is 2 hours. You will find in detail deploymen
 ```
 
 <br/>
-<img width="50%" src="../images/policy-1.png">
+![Policy 1](../images/policy-1.png)
 
   * Give the policy the name **AWSMarketplacePolicyForCloudFormation** and click **Create Policy**.
 
 <br/>
-<img width="50%" src="../images/policy-2.png">  
+![Policy 2](../images/policy-2.png)  
 
 
 
@@ -385,20 +385,20 @@ The expiry time for this installer is 2 hours. You will find in detail deploymen
   * Select **Trusted entity** type: `AWS service`.
   * Select **Use case**: `CloudFormation` and click **Next**.
 <br/>
-<img width="50%" src="../images/policy-3.png">
+![Policy 3](../images/policy-3.png)
   * Search for and select the **AWSMarketplacePolicyForCloudFormation** policy you just created, then click **Next**.
   <br/>
-<img width="50%" src="../images/policy-4.png">
+![Policy 4](../images/policy-4.png)
   * Name the role **AWSMarketplaceMeteringRoleForCloudFormation** and click **Create role**.
 <br/>
-<img width="50%" src="../images/policy-5.png">
+![Policy 5](../images/policy-5.png)
 
 
 ### Step 3: PassRole Permission
 
   * Copy the **Role ARN** of the role you just created: `arn:aws:iam::xxxxxxxx:role/AWSMarketplaceMeteringRoleForCloudFormation`.
  <br/>
-<img width="50%" src="../images/policy-7.png"> 
+![Policy 7](../images/policy-7.png) 
 
 
 
@@ -424,7 +424,7 @@ The expiry time for this installer is 2 hours. You will find in detail deploymen
 ```
 
 <br/>
-<img width="50%" src="../images/policy-8.png"> 
+![Policy 8](../images/policy-8.png) 
 
 
 
@@ -433,7 +433,7 @@ The expiry time for this installer is 2 hours. You will find in detail deploymen
   * Provide a name for this policy (e.g., **AllowPassingMeterUsageRoleToCloudFormation**) and click **Create policy**.
   
    <br/>
-<img width="50%" src="../images/policy-9.png"> 
+![Policy 9](../images/policy-9.png) 
 
 
 
@@ -444,7 +444,7 @@ The expiry time for this installer is 2 hours. You will find in detail deploymen
   * Select the **AllowPassingMeterUsageRoleToCloudFormation** policy you just created to attach it.
 
  <br/>
-<img width="50%" src="../images/policy-10.png"> 
+![Policy 10](../images/policy-10.png) 
 
 Now follow the steps to configure the stack
 
@@ -455,22 +455,22 @@ and subscribe to **AppsCode Cloud w/Usage Billing** product.
   * Click on Continue To Configuration.
 
  <br/>
-<img width="50%" src="../images/awsStep1.png"> 
+![Aws Step 1](../images/awsStep1.png) 
 
 ### Step 2: Configuration
 
   * Select the latest software version, and region for the Application and click on **Continue to Launch.**
 
  <br/>
-<img width="50%" src="../images/awsStep2.png"> 
+![Aws Step 2](../images/awsStep2.png) 
 
 ### Step 3: Create stack
 
   * You will be forwarded to the Cloudformation selection page.
   * Keep the default selected template and click on **Next.**
 
  <br/>
-<img width="50%" src="../images/awsStep3.png"> 
+![Aws Step 3](../images/awsStep3.png) 
 
 ### Step 4: Specify stack details
 
@@ -482,15 +482,15 @@ and subscribe to **AppsCode Cloud w/Usage Billing** product.
   * Click **Next** and you will be forwarded to the **review and create page.**
 
  <br/>
-<img width="50%" src="../images/awsStep4.png"> 
+![Aws Step 4](../images/awsStep4.png) 
 
 ### Step 5: Attach role to CloudFormation (Optional)
 
   * **Prerequisite:** You must have IAM roles for this.
   * When applying the cloudformation template (CFT), attach **AWSMarketplaceMeteringRoleForCloudFormation** role to the template. This way the CFT will have all the necessary permission to deploy the resources.
 
  <br/>
-<img width="50%" src="../images/awsStep5.png"> 
+![Aws Step 5](../images/awsStep5.png) 
 
 ### Step 6: Review & Deployment
 
@@ -499,7 +499,7 @@ and subscribe to **AppsCode Cloud w/Usage Billing** product.
   * Once the Cloudformation is created it will take **5-10min** to spin up the application.
 
  <br/>
-<img width="50%" src="../images/awsStep7.png"> 
+![Aws Step 7](../images/awsStep7.png) 
 
 ### 10. Explore the Deployed Platform
 
diff --git a/docs/platform/selfhost-setup/install/azure-marketplace.md b/docs/platform/selfhost-setup/install/azure-marketplace.md
@@ -85,7 +85,7 @@ See [Monitoring](common-config.md#monitoring) in the Common Configuration guide
 * Put Login and Logout URL 
 
 <br/>
-<img width="50%" src="../images/domain-whitelisting.png">
+![Domain Whitelisting](../images/domain-whitelisting.png)
 
 ### 8. Self Management
 
@@ -105,38 +105,37 @@ Click the "Deploy" button to submit your information. KubeDB Platform will gener
 Go to Azure Marketplace and select AppsCode Cloud w/ Usage Billing application. [AppsCode Cloud w/ Usage Billing from Marketplace](https://portal.azure.com/#create/appscode.ace_paygace-payg)
 
 <br/>
-<img width="50%" src="../images/azureStep1.png">
+![Azure Step 1](../images/azureStep1.png)
 
 #### Step 2: Basic Information
 Provide basic information for the Azure application. Put your resource group and application name. 
 
 <br/>
-<img width="50%" src="../images/azureStep2.png">
+![Azure Step 2](../images/azureStep2.png)
 
 #### Step 3: Select VM
 Select a virtual machine for the Installer with at least 4 core CPU and 16GB of RAM.
 
 <br/>
-<img width="50%" src="../images/azureStep3.png">
+![Azure Step 3](../images/azureStep3.png)
 
 #### Step 4: Authentication Type
 By default Username user will be created to your Installer VM.
 You can use one of the Password or SSH Key Pair to authenticate into the VM.
 
 <br/>
-<img width="50%" src="../images/azureStep4.png">
+![Azure Step 4](../images/azureStep4.png)
 
 #### Step 5: Installer Information
 Provide the URL link you found from the instruction in the Installer Url field
 
 <br/>
-<img width="50%" src="../images/azureStep5.png">
+![Azure Step 5](../images/azureStep5.png)
 
 You can monitor the deployment progress through the **Managed Resource Group's** overview page and the **Activity Log**. Once the deployment is complete, the necessary resources will be provisioned within that managed resource group.
-<div style="display: flex; justify-content: space-between;">
-  <img src="../images/ace-status.png" style="width: 48%;">
-  <img src="../images/managed-resources.png" style="width: 48%;">
-</div>
+![Ace Status](../images/ace-status.png)
+
+![Managed Resources](../images/managed-resources.png)
 
 ### 12. Explore the Deployed Platform
 
diff --git a/docs/platform/selfhost-setup/install/cloud-demo.md b/docs/platform/selfhost-setup/install/cloud-demo.md
@@ -80,7 +80,7 @@ Follow the documentation provided by AppsCode to deploy the KubeDB Platform on y
 Once deployed, access the KubeDB Platform using the specified domain. Log in with the admin account credentials provided during the creation process.
 
 <br/>
-<img width="50%" src="../images/ace-dashboard.png">
+![Ace Dashboard](../images/ace-dashboard.png)
 
 ## Get Support
 
diff --git a/docs/platform/selfhost-setup/install/common-config.md b/docs/platform/selfhost-setup/install/common-config.md
@@ -48,7 +48,7 @@ Use the **Monitoring** section to configure Alertmanager notifications for platf
   * **Send Resolved:** Sends a follow-up notification when an alert returns to a healthy state.
 
 <br/>
-<img width="50%" src="../images/monitoring-alertmanager.png">
+![Monitoring Alertmanager](../images/monitoring-alertmanager.png)
 
 > **Tip:** For Google Chat, a supported workaround is to generate a space email address in Google Chat settings and use that address in the **To** field.
 
@@ -79,7 +79,7 @@ Configure NATS, which is used as the internal messaging system for the platform.
 **Resources:** Configure CPU Requests, CPU Limits, Memory Request and  Memory Limit
 
 <br/>
-<img width="50%" src="../images/nats.png">
+![Nats](../images/nats.png)
 
 ## Branding & UI Customization
 
@@ -93,7 +93,7 @@ Administrators can globally re-brand the KubeDB Platform interface to match corp
 * **App Tag:** Toggle **"Show App Tag"** to display or hide the version/tagging info in the UI.
 
 <br/>
-<img width="50%" src="../images/branding.png">
+![Branding](../images/branding.png)
 
 
 ## Prerequisites
@@ -117,7 +117,7 @@ These credentials define the primary super-user and the initial organizational s
   - **Initial Organization Name:** You can choose what will be the initial organization name for your account
 
 <br/>
-<img width="50%" src="../images/admin-setting.png">
+![Admin Setting](../images/admin-setting.png)
 
 ## Additional configuration for EKS cluster
 
@@ -148,7 +148,7 @@ aws ec2 describe-subnets --filters "Name=vpc-id,Values=$(aws eks describe-cluste
 * Put Login and Logout URL for your app
 
 <br/>
-<img width="50%" src="../images/domain-whitelisting.png">
+![Domain Whitelisting](../images/domain-whitelisting.png)
 
 ## Ingress & Gateway
 
@@ -157,11 +157,11 @@ Configure how the application is exposed to the internet or your internal networ
 * **Ingress & Gateway:** Enable either the **Gateway API** or standard **Ingress**.
 
 <br/>
-<img width="50%" src="../images/ingress-gateway.png">
+![Ingress Gateway](../images/ingress-gateway.png)
 
 ## Self Management
 
 In this section you can enable or disable features.
 
 <br/>
-<img width="50%" src="../images/features.png">
+![Features](../images/features.png)
diff --git a/docs/platform/selfhost-setup/install/onprem-demo.md b/docs/platform/selfhost-setup/install/onprem-demo.md
@@ -83,7 +83,7 @@ Follow the documentation provided by AppsCode to deploy the KubeDB Platform on y
 Once deployed, access the KubeDB Platform using the specified domain. Log in with the admin account credentials provided during the creation process.
 
 <br/>
-<img width="50%" src="../images/ace-dashboard.png">
+![Ace Dashboard](../images/ace-dashboard.png)
 
 ## Get Support
 
diff --git a/docs/platform/selfhost-setup/install/openshift-cluster.md b/docs/platform/selfhost-setup/install/openshift-cluster.md
@@ -99,14 +99,14 @@ Follow the documentation provided by AppsCode to deploy the KubeDB Platform on y
 4. **Run the remaining install steps.** Continue with the rest of the generated instructions (flux install, `helm upgrade`, and the ACE install) using the reconfigured values.
 
 <br/>
-<img width="80%" src="../images/ip-reconfigure-openshift.png">
+![Ip Reconfigure Openshift](../images/ip-reconfigure-openshift.png)
 
 ### 6. Explore the Deployed Platform
 
 Once deployed, access the **KubeDB Platform** using the configured IP (IP mode) or domain (DNS mode). Log in with the admin account credentials provided during the creation process.
 
 <br/>
-<img width="50%" src="../images/ace-dashboard.png">
+![Ace Dashboard](../images/ace-dashboard.png)
 
 ## Notes
 
diff --git a/docs/platform/selfhost-setup/install/selfhosted-production.md b/docs/platform/selfhost-setup/install/selfhosted-production.md
@@ -50,7 +50,7 @@ Before beginning the installation, identify your target infrastructure and clust
 * **Cluster Type:** Determine if you are installing on **AWS EKS Cluster** or **Red Hat OpenShift Cluster**. For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint. See the [Deploying KubeDB Platform in OpenShift Cluster](openshift-cluster.md) guide.
 * **Credential-Less Mode:** Enable this if you are using IAM roles for service accounts (IRSA) to avoid manual secret management.
 <br/>
-<img width="50%" src="../images/selfhost-deployment-option.png">
+![Selfhost Deployment Option](../images/selfhost-deployment-option.png)
 
 ### Additional configuration for EKS cluster
 
@@ -184,7 +184,7 @@ See [Registry](common-config.md#registry) in the Common Configuration guide for
 This secton is for Persistence & Resource Allocation. Properly sizing your resources is critical for production stability. Configure CPU Requests, CPU Limits, Memory Request and  Memory Limit for both cache and Database
 
 
-<img width="50%" src="../images/resource-limit.png">
+![Resource Limit](../images/resource-limit.png)
 <br/>
 
 > [!IMPORTANT]
@@ -248,4 +248,4 @@ Follow the documentation provided by AppsCode to deploy the KubeDB Platform on y
 Once deployed, access the **KubeDB Platform** using the specified domain. Log in with the admin account credentials provided during the creation process.After the login process you will see the **KubeDB Platform dashboard** user interface
 
 <br/>
-<img width="50%" src="../images/ace-dashboard.png">
+![Ace Dashboard](../images/ace-dashboard.png)
