Merge branch 'CHAOS-7287' of https://github.com/harness/developer-hub …

…into CHAOS-7287

.github/CODEOWNERS

@@ -50,12 +50,12 @@ static/  @rohanmaharjan100 @wei-harness
 # data/*.ts @global-data-file-owners
 
 # Continuous Delivery Docs
-/docs/continuous-delivery/ @krishi0408 @SushrutHarness @vishal-av @pranaykaikini @prasadsatamharness
-/release-notes/continuous-delivery.md @krishi0408 @SushrutHarness @vishal-av @pranaykaikini @prasadsatamharness
-/src/components/Roadmap/data/cdData.ts @krishi0408 @SushrutHarness @vishal-av
-/src/components/Docs/data/continuousDeliveryData*  @krishi0408 @SushrutHarness @vishal-av
+/docs/continuous-delivery/ @krishi0408 @SushrutHarness @vishal-av @pranaykaikini @prasadsatamharness @thisrohangupta
+/release-notes/continuous-delivery.md @krishi0408 @SushrutHarness @vishal-av @pranaykaikini @prasadsatamharness @thisrohangupta
+/src/components/Roadmap/data/cdData.ts @krishi0408 @SushrutHarness @vishal-av @thisrohangupta
+/src/components/Docs/data/continuousDeliveryData*  @krishi0408 @SushrutHarness @vishal-av @thisrohangupta
 # FirstGen CD Docs
-/docs/category/continuous-delivery/ @krishi0408 @SushrutHarness @vishal-av
+/docs/category/continuous-delivery/ @krishi0408 @SushrutHarness @vishal-av @thisrohangupta
 # CD FAQs
 /docs/faqs/continuous-delivery-faqs @krishi0408 @SushrutHarness @vishal-av
 # GitEx FAQs
@@ -105,12 +105,12 @@ static/  @rohanmaharjan100 @wei-harness
 /src/components/Docs/data/serviceReliabilityManagementData.ts @sunilgupta-harness
 
 # Chaos Docs
-/docs/chaos-engineering/ @neelanjan00 @SmritiSatya @shovanmaity @Jonsy13 @Saranya-jena @Adarshkumar14 @ispeakc0de @amityt @uditgaurav @S-ayanide @vanshBhatia-A4k9
+/docs/chaos-engineering/ @neelanjan00 @SmritiSatya @shovanmaity @Jonsy13 @Saranya-jena @Adarshkumar14 @ispeakc0de @amityt @uditgaurav @S-ayanide @vanshBhatia-A4k9 @ksatchit @umamukkara
 /release-notes/chaos-engineering.md @neelanjan00 @SmritiSatya @Jonsy13
 /src/components/Roadmap/data/ceData.ts @krishi0408 @neelanjan00 @SmritiSatya @vishal-av @SushrutHarness
 /src/components/Docs/data/chaosEngineeringData* @krishi0408 @neelanjan00 @SmritiSatya @vishal-av @SushrutHarness
 # Chaos FAQs
-/kb/chaos-engineering/chaos-engineering-faq @neelanjan00 @SmritiSatya @ksatchit
+/kb/chaos-engineering/chaos-engineering-faq @neelanjan00 @SmritiSatya @ksatchit @umamukkara
 
 # Incident Response Docs
 /docs/incident-response/ @SmritiSatya 

.github/workflows/markdown-file-validation.yaml → .github/workflows/markdown-and-image-file-validation.yaml

@@ -69,4 +69,4 @@ jobs:
           else
             echo -e "${Red} The check has failed.${Reset}"
             exit 1
-          fi
+          fi

client-modules/searchBar.js

@@ -0,0 +1,78 @@
+import ExecutionEnvironment from '@docusaurus/ExecutionEnvironment';
+
+const doYourCustomStuff = () => {
+  const navbar__items = document.querySelector('.navbar__items');
+  const navbar__sidebar__close = document.querySelector(
+    '.navbar-sidebar__close'
+  );
+  const navbar__inner = document.querySelector('.navbar__inner');
+
+  const searchBoxMain = navbar__inner.querySelector('#coveo-search-main');
+
+  if (searchBoxMain) {
+    searchBoxMain.classList.add('main-nav-coveo');
+  }
+
+  const searchButton = document.createElement('i');
+  searchButton.setAttribute('id', 'search-button');
+  searchButton.setAttribute('class', 'fa-solid fa-magnifying-glass');
+
+  if (navbar__items) {
+    navbar__items.appendChild(searchButton);
+    if (window.location.pathname !== '/') {
+      const navbar__toggle = document.querySelectorAll('.navbar__toggle');
+      if (navbar__toggle) {
+        navbar__toggle[0].addEventListener('click', () => {
+          const navbar__sidebar__items = document.querySelectorAll(
+            '.navbar-sidebar__items'
+          );
+          if (navbar__sidebar__items[0]) {
+            navbar__sidebar__items[0].classList.add(
+              'navbar-sidebar__items--show-secondary'
+            );
+          }
+        });
+      }
+    }
+
+    searchButton.addEventListener('click', () => {
+      const navbar = document.querySelector('.navbar');
+      const navbar__sidebar = document.querySelector('.navbar-sidebar');
+
+      if (navbar && navbar__sidebar) {
+        navbar.classList.add('navbar-sidebar--show');
+        navbar__sidebar.classList.add('navbar-sidebar--show');
+      }
+
+      const navbar__sidebar__items = document.querySelectorAll(
+        '.navbar-sidebar__items'
+      );
+      if (navbar__sidebar__items[0]) {
+        navbar__sidebar__items[0].classList.remove(
+          'navbar-sidebar__items--show-secondary'
+        );
+      }
+    });
+  }
+  if (navbar__sidebar__close) {
+    navbar__sidebar__close.addEventListener('click', () => {
+      const navbar = document.querySelector('.navbar');
+      const navbar__sidebar = document.querySelector('.navbar-sidebar');
+
+      if (navbar && navbar__sidebar) {
+        navbar.classList.remove('navbar-sidebar--show');
+        navbar__sidebar.classList.remove('navbar-sidebar--show');
+      }
+    });
+  }
+};
+
+if (ExecutionEnvironment.canUseDOM) {
+  window.addEventListener('load', () => {
+    setInterval(doYourCustomStuff, 500);
+    // setTimeout(() => {
+    //   clearInterval(interval);
+    //   interval = 0;
+    // }, 2000);
+  });
+}

docs/artifact-registry/manage-registries/create-registry.md

@@ -39,13 +39,24 @@ An **Upstream Proxy** for an **Artifact Registry** is a proxy configuration that
     - Enter the proxy <b>Source</b>. Either <b>Docker Hub</b> or a <b>Custom</b> source.
     - If it's a custom source, enter the Docker <b>Remote Registry URL</b>. 
     </TabItem>
+    <TabItem value="ECR" label="ECR">
+    - Select the **AWS ECR** source
+    - Enter the **ECR Remote Registy URL**
 
+    :::info AWS ECR info
+    This will in be your AWS Elastic Container Registry (ECR) repositories, e.g. `https://{region}.console.aws.amazon.com/ecr/repositories/{public-or-private}/{repo-id}/{repo-name}?region={region}`    
+    :::
+    </TabItem>
     <TabItem value="Helm" label="Helm">
     Enter the Helm <b>Remote Registry URL</b>.
     </TabItem>
     </Tabs>
+    ---
 
 1. Choose your **Authentication** method.
-1. Select **Create Upstream Proxy**.
+:::note public vs private authentication
+Select `Access Key and Secret Key` for private sources and `Anonymous (No credentials required)` for public sources.
+:::
 
-After you've created your upstream proxy you will need to set it in a registry. To learn how to do so, go to [Set an upstream proxy](/docs/artifact-registry/manage-registries/configure-registry#set-an-upstream-proxy).
+1. Select **Create Upstream Proxy**.
+After you've created your upstream proxy you will need to set it in a registry. To learn how to do so, go to [Set an upstream proxy](/docs/artifact-registry/manage-registries/configure-registry#set-an-upstream-proxy).

docs/artifact-registry/troubleshooting/_category_.json

@@ -0,0 +1,9 @@
+{
+    "label": "Troubleshooting",
+    "collapsible": "false",
+    "collapsed": "true",
+    "link": { "type": "generated-index", "title": "Troubleshooting" },
+    "customProps": {},
+    "position": 60
+  }
+

docs/artifact-registry/troubleshooting/authorization/_category_.json

@@ -0,0 +1,8 @@
+{
+    "label": "Authorization / Authentication",
+    "collapsible": "true",
+    "collapsed": "false",
+    "link": { "type": "generated-index", "title": "Authorization / Authentication" },
+    "customProps": {},
+    "position": 10
+  }

docs/artifact-registry/troubleshooting/authorization/auth-401-errors.md

@@ -0,0 +1,54 @@
+---
+title: Issues Pulling Images
+description: Fixing 401 Unauthorized errors when pulling images from Harness Artifact Registry.
+sidebar_position: 10
+---
+
+This document provides steps to resolve "401 Unauthorized" errors when pulling images from Harness Artifact Registry.
+
+## Understanding 401 Errors When Pulling Images
+
+401 Unauthorized errors occur when Harness Artifact Registry fails to authenticate image pull requests from the Kubernetes cluster.
+
+:::tip Cluster Secrets
+Ensure your cluster has the correct `imagePullSecrets` and Kubernetes secrets configured.
+:::
+
+### Example Solution
+
+To authenticate your Kubernetes cluster, follow these steps:
+
+1. **Create a Docker Registry Secret:**
+
+   ```bash
+   kubectl create secret docker-registry docker-registry-secret1 \
+   --docker-server=pkg.harness.io \
+   --docker-username=<email> \
+   --docker-password=<personal-access-token> \
+   --docker-email=<email> \
+   --namespace=default
+   ```
+
+2.	**Update your Kubernetes deployment manifest to reference the secret:**
+  ```bash
+  apiVersion: v1
+  kind: Pod
+  metadata:
+    name: your-pod-name
+    namespace: default
+  spec:
+    containers:
+      - name: your-container-name
+        image: pkg.harness.io/your-image:tag
+    imagePullSecrets:
+      - name: docker-registry-secret1
+  ```
+
+3.	**Verify the Setup:**
+
+Deploy the updated manifest and monitor the pod status to ensure the image is pulled successfully without authentication errors.
+
+---
+
+## Kubernetes-specific guides
+Go to the [Private Registry for Kubernetes guide](https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/kubernetes/cd-kubernetes-category/pull-an-image-from-a-private-registry-for-kubernetes/) or [Add Container Images as Artifacts](https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/kubernetes/cd-kubernetes-category/add-artifacts-for-kubernetes-deployments/) for more details on how to pull an image from a private registry, or to add container images as artifacts for Kubernetes deployments.

docs/artifact-registry/troubleshooting/authorization/auth-403-errors.md

@@ -0,0 +1,16 @@
+---
+title: 403 Errors in Pipeline Execution
+description: Troubleshooting common 403 errors during pipeline execution in Harness Artifact Registry.
+sidebar_position: 20
+---
+
+This document helps you troubleshoot 403 errors encountered during pipeline execution.
+
+## Understanding 403 Errors in Pipeline Execution
+403 errors typically indicate a permissions or access-related issue in your pipeline setup. They may arise due to configuration changes or mismatched access credentials. Go to [role-based access control (RBAC)](https://developer.harness.io/docs/platform/role-based-access-control/rbac-in-harness) to find out how to manage pipeline permissions.
+
+:::tip account level access
+Check if any recent changes to account-level flags or permissions may have impacted the pipeline.
+:::
+
+Go to the [permission reference](https://developer.harness.io/docs/platform/role-based-access-control/permissions-reference/) to review the specific permissions required for your pipeline execution.

docs/chaos-engineering/integrations/pipeline-exec.md

@@ -34,7 +34,7 @@ To execute an experiment in a pipeline, you need to have the appropriate permiss
 
 ### Integrate Experiment Pipeline with Notification
 
-You can create a chaos experiment as a pipeline and integrate it to receive notifications about the status of the experiment. Go to [create experiment as a pipeline](/docs/chaos-engineering/use-harness-ce/experiments/create-experiments#create-experiment-as-a-pipeline) to get hands-on experience of creating a chaos experiment as a pipeline.
+You can create a chaos experiment (on **Kubernetes dedicated infrastructure**, **Harness Delegate**, **Linux**, or **Windows infrastructure**) as a pipeline and integrate it to receive notifications about the status of the experiment. Go to [create experiment as a pipeline](/docs/chaos-engineering/use-harness-ce/experiments/create-experiments#create-experiment-as-a-pipeline) to create a chaos experiment as a pipeline.
 
 For more information, go to [Pipeline concepts](/docs/continuous-integration/get-started/key-concepts) and [Pipeline Modeling Overview](/docs/continuous-delivery/get-started/cd-pipeline-modeling-overview).
 

docs/chaos-engineering/use-harness-ce/application-map.md

@@ -63,10 +63,11 @@ You can [create](#create-application-map), [edit](#edit-application-map), and [d
     ![](./static/app-maps/save-nw-5.png)
 
 :::info note
-To view chaos-enabled experiment map, navigate to **Chaos** module and select **Application Maps**.
+- To view chaos-enabled experiment map, navigate to **Chaos** module and select **Application Maps**.
 
     ![](./static/app-maps/create-nw-1.png)
 
+- To manually associate the experiment as a part of an application map, specify the tag `applicationmap=<application map identity>` in the experiment.
 :::
 
 ### Edit application map

docs/chaos-engineering/use-harness-ce/chaos-faults/aws/aws.md

@@ -786,6 +786,21 @@ Lambda delete event source mapping removes the event source mapping from an AWS
 
 <FaultDetailsCard category="aws">
 
+### Lambda function layer detach
+
+Lambda function layer detach is an AWS fault that detaches the Lambda layer associated with the function, thereby causing dependency-related issues or breaking the Lambda function that relies on the layer's content.
+
+<Accordion color="green">
+<summary>Use cases</summary>
+
+- Debug runtime errors caused by a specific library in the layer.
+- Tests how the Lambda function behaves without the dependencies provided by the layer, thereby identifying the unnecessary dependencies and reduce the layer's footprint.
+
+</Accordion>
+</FaultDetailsCard>
+
+<FaultDetailsCard category="aws">
+
 ### Lambda delete function concurrency
 
 Lambda delete function concurrency deletes the Lambda function's reserved concurrency, thereby ensuring that the function has adequate unreserved concurrency to run.

docs/chaos-engineering/use-harness-ce/chaos-faults/aws/experiments.ts

@@ -309,6 +309,13 @@ export const experiments: ExperimentDetails[] = [
     tags: ['lambda', 'delete', 'concurrency'],
     category: "aws",
   },
+  {
+    name: "Lambda function layer detach",
+    description:
+      "Lambda function layer detach is an AWS fault that detaches the Lambda layer associated with the function, thereby causing dependency-related issues or breaking the Lambda function that relies on the layer's content.",
+    tags: ['lambda', 'detach', 'function'],
+    category: "aws",
+  },
   {
     name: "Lambda toggle event mapping state",
     description: