KubeRocketCI · SergK · Mar 2, 2025 · Mar 2, 2025
diff --git a/docs/developer-guide/aws-reference-architecture.md b/docs/developer-guide/aws-reference-architecture.md
@@ -5,7 +5,6 @@ sidebar_label: "KubeRocketCI Reference Architecture on AWS"
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # KubeRocketCI Reference Architecture on AWS
 
 <head>

diff --git a/docs/operator-guide/advanced-installation/overview.md b/docs/operator-guide/advanced-installation/overview.md
@@ -7,7 +7,6 @@ sidebar_label: "Overview"
 
 # Advanced Installation Overview: Third-Party Tools
 
-
 <head>
   <link rel="canonical" href="https://docs.kuberocketci.io/docs/operator-guide/advanced-installation" />
 </head>

diff --git a/docs/operator-guide/cd/argocd-integration.md b/docs/operator-guide/cd/argocd-integration.md
@@ -301,7 +301,6 @@ This section provides the information on how to test the integration with Argo C
 
     </details>
 
-
 2. Check that your new Application is added to the Argo CD UI under the `edp` Project scope.
 
 ## Deploy Argo CD Application to Remote Cluster (Optional)

diff --git a/docs/operator-guide/cd/deploy-rpm.md b/docs/operator-guide/cd/deploy-rpm.md
@@ -28,13 +28,12 @@ In KubeRocketCI, RPM support allows to collect applications, store them as Nexus
 - **Customizable Task Execution**: Offers flexible configuration of task execution sequences.
 - **No UI**: Operates entirely without a graphical user interface, relying on code-based configurations.
 
-#### AWX Operator:
+#### AWX Operator
 
 - **User-Friendly Interface**: Features a convenient UI for managing configurations and tasks.
 - **Partial Code-Based Configurations**: Retrieves some configurations (such as Ansible tasks) directly from the repository.
 - **UI-Based Configuration**: All configurations are performed within the graphical user interface.
 
-
 ## Default Approach
 
 The first method to delivery RPM packages is using KubeRocketCI RPM deploy pipeline.
@@ -171,7 +170,6 @@ Below is a structure of a GitOps repository designed for deploying RPM packages:
     ```
     </details>
 
-
 The main configuration files description:
 
 - **nexus.repo**: Contains the configuration for connecting to Nexus, to pull artifacts to the instance.
@@ -246,7 +244,6 @@ To set up RPM integration using AWX tool, follow the steps below. Completing the
       ```
     </details>
 
-
     Here is a breakdown of the scheme above:
 
     * **package-install.yaml**: This is the main file that refers to playbooks located in the **roles** directory.
@@ -315,7 +312,6 @@ To set up RPM integration using AWX tool, follow the steps below. Completing the
 
       ![AWX template](../../assets/operator-guide/rpm/awx-template.png "AWX template")
 
-
 4. Create application with the **rpm-package** deployment option. Refer to the [Add Application](../../user-guide/add-application.md) page for more details:
 
   ![Create RPM application](../../assets/operator-guide/rpm/rpm.gif "Create RPM application")

diff --git a/docs/operator-guide/ci/tekton-monitoring.md b/docs/operator-guide/ci/tekton-monitoring.md
@@ -90,17 +90,16 @@ As soon as the dashboard procedure is completed, you can track the newcoming met
 The [edp-install](https://github.com/epam/edp-install/) helm chart allows to integrate tekton-pipelines metrics with the Prometheus and Grafana stack through the `edp-tekton.grafana.enabled` field in [values.yaml](https://github.com/epam/edp-install/blob/d149baeb9756bdf113996620630f9b04f896e08d/deploy-templates/values.yaml#L309) file.
 To enable integration, set the `edp-tekton.grafana.enabled` field to `true` and apply the changes to the cluster.
 
-    ```yaml values.yaml
-    edp-tekton:
-      grafana:
-        enabled: true
-    ```
+  ```yaml values.yaml
+  edp-tekton:
+    grafana:
+      enabled: true
+  ```
 
 After the changes are applied, the tekton-pipelines metrics will be available in the `KRCI Tekton overview` Grafana dashboard:
 
     ![Tekton dashboard](../../assets/operator-guide/grafana-dashboard-is-created.png "Tekton dashboard is created")
 
-
 ## Related Articles
 
 * [Install Tekton](../install-tekton.md)

diff --git a/docs/operator-guide/devsecops/dependency-track.md b/docs/operator-guide/devsecops/dependency-track.md
@@ -14,7 +14,6 @@ import TabItem from '@theme/TabItem';
   <link rel="canonical" href="https://docs.kuberocketci.io/docs/operator-guide/devsecops/dependency-track" />
 </head>
 
-
 This documentation guide provides comprehensive instructions for installing and integrating Dependency-Track with the KubeRocketCI.
 
 ## Prerequisites

diff --git a/docs/operator-guide/microsoft-entra/grafana-authentication.md b/docs/operator-guide/microsoft-entra/grafana-authentication.md
@@ -7,7 +7,6 @@ sidebar_label: "Grafana"
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # Guide: Microsoft Entra SSO Integration With Grafana
 
 <head>

diff --git a/docs/operator-guide/project-management-and-reporting/jira-integration.md b/docs/operator-guide/project-management-and-reporting/jira-integration.md
@@ -133,8 +133,6 @@ In order to adjust the Jira server integration, add the JiraServer CR by perform
       3. **Add Comments:** Required for adding external links and comments to issues.
     :::
 
-
-
 ## Enable Jira During Platform Deployment
 
 KubeRocketCI offers the capability to incorporate Jira integration as part of its deployment process. To follow this approach, please review the following parameters of the [values.yaml](https://github.com/epam/edp-install/blob/release/3.9/deploy-templates/values.yaml#L145) file. Enabling the `jira.integration` parameter creates the following custom resources:

diff --git a/docs/operator-guide/upgrade/upgrade-edp-3.5.md b/docs/operator-guide/upgrade/upgrade-edp-3.5.md
@@ -16,7 +16,6 @@ import TabItem from '@theme/TabItem';
   <link rel="canonical" href="https://docs.kuberocketci.io/docs/operator-guide/upgrade/upgrade-edp-3.5" />
 </head>
 
-
 :::warning
   We suggest making a backup of the EDP environment before starting the upgrade procedure.
 :::

diff --git a/docs/user-guide/add-git-server.md b/docs/user-guide/add-git-server.md
@@ -119,6 +119,7 @@ For [Bitbucket](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords
    ```bash
    echo -n "username:AppPassword" | base64
    ```
+
    :::
 
     <Tabs

diff --git a/docs/user-guide/components.md b/docs/user-guide/components.md
@@ -7,7 +7,6 @@ description: "Explore the essentials of codebases and onboarding strategies in K
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # Components: Codebases and Onboarding Strategies
 
 <head>

diff --git a/docs/user-guide/gitops.md b/docs/user-guide/gitops.md
@@ -7,7 +7,6 @@ sidebar_label: "Manage Clusters"
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # Manage GitOps
 
 <head>

diff --git a/faq/how-to/application-deployment/change-environment-variables-redeploy.md b/faq/how-to/application-deployment/change-environment-variables-redeploy.md
@@ -4,7 +4,6 @@
   <link rel="canonical" href="https://docs.kuberocketci.io/faq/how-to/application-deployment/change-environment-variables-redeploy" />
 </head>
 
-
 KubeRocketCI leverages Helm charts for application deployments, with each application repository including a Helm chart located in the `deploy-templates` folder. This chart defines the default parameters used during deployment.
 
 To customize parameters for a specific environment, a `values.yaml` file is utilized. This file provides flexibility by allowing environment-specific configurations without altering the default settings. Instead of modifying parameters directly within the `deploy-templates` directory, which we strongly discourage, a structured approach is followed by managing the `values.yaml` file in the `krci-gitops` repository. This ensures a clean and maintainable configuration process for Helm chart deployments.

diff --git a/versioned_docs/version-3.10/operator-guide/advanced-installation/overview.md b/versioned_docs/version-3.10/operator-guide/advanced-installation/overview.md
@@ -7,7 +7,6 @@ sidebar_label: "Overview"
 
 # Advanced Installation Overview: Third-Party Tools
 
-
 <head>
   <link rel="canonical" href="https://docs.kuberocketci.io/docs/operator-guide/advanced-installation/overview" />
 </head>

diff --git a/versioned_docs/version-3.10/operator-guide/auth/configure-keycloak-oidc-eks.md b/versioned_docs/version-3.10/operator-guide/auth/configure-keycloak-oidc-eks.md
@@ -104,7 +104,6 @@ The initial step involves setting up the Keycloak operator (configure connection
       enable: true
     ```
 
-
 This add-ons facilitates sets up a broker realm to manage traffic redirection between external Identity Providers (IdP) and internal clients. Additionally, it creates a shared realm that encompasses all clients, including to EKS, Sonar, Nexus, and Portal.
 
 The [KubeRocketCI RBAC add-on](https://github.com/epam/edp-cluster-add-ons/tree/main/clusters/core/addons/kuberocketci-rbac) creates Keycloak groups that are used in the KubeRocketCI platform to manage access to resources. For more details refer to the [KubeRocketCI Groups](platform-auth-model.md#groups) documentation.

diff --git a/versioned_docs/version-3.10/operator-guide/cd/argocd-integration.md b/versioned_docs/version-3.10/operator-guide/cd/argocd-integration.md
@@ -301,7 +301,6 @@ This section provides the information on how to test the integration with Argo C
 
     </details>
 
-
 2. Check that your new Application is added to the Argo CD UI under the `edp` Project scope.
 
 ## Deploy Argo CD Application to Remote Cluster (Optional)

diff --git a/versioned_docs/version-3.10/operator-guide/cd/deploy-rpm.md b/versioned_docs/version-3.10/operator-guide/cd/deploy-rpm.md
@@ -28,13 +28,12 @@ In KubeRocketCI, RPM support allows to collect applications, store them as Nexus
 - **Customizable Task Execution**: Offers flexible configuration of task execution sequences.
 - **No UI**: Operates entirely without a graphical user interface, relying on code-based configurations.
 
-#### AWX Operator:
+#### AWX Operator
 
 - **User-Friendly Interface**: Features a convenient UI for managing configurations and tasks.
 - **Partial Code-Based Configurations**: Retrieves some configurations (such as Ansible tasks) directly from the repository.
 - **UI-Based Configuration**: All configurations are performed within the graphical user interface.
 
-
 ## Default Approach
 
 The first method to delivery RPM packages is using KubeRocketCI RPM deploy pipeline.
@@ -171,7 +170,6 @@ Below is a structure of a GitOps repository designed for deploying RPM packages:
     ```
     </details>
 
-
 The main configuration files description:
 
 - **nexus.repo**: Contains the configuration for connecting to Nexus, to pull artifacts to the instance.
@@ -246,7 +244,6 @@ To set up RPM integration using AWX tool, follow the steps below. Completing the
       ```
     </details>
 
-
     Here is a breakdown of the scheme above:
 
     * **package-install.yaml**: This is the main file that refers to playbooks located in the **roles** directory.
@@ -315,7 +312,6 @@ To set up RPM integration using AWX tool, follow the steps below. Completing the
 
       ![AWX template](../../assets/operator-guide/rpm/awx-template.png "AWX template")
 
-
 4. Create application with the **rpm-package** deployment option. Refer to the [Add Application](../../user-guide/add-application.md) page for more details:
 
   ![Create RPM application](../../assets/operator-guide/rpm/rpm.gif "Create RPM application")

diff --git a/versioned_docs/version-3.10/operator-guide/ci/tekton-monitoring.md b/versioned_docs/version-3.10/operator-guide/ci/tekton-monitoring.md
@@ -100,7 +100,6 @@ After the changes are applied, the tekton-pipelines metrics will be available in
 
     ![Tekton dashboard](../../assets/operator-guide/grafana-dashboard-is-created.png "Tekton dashboard is created")
 
-
 ## Related Articles
 
 * [Install Tekton](../install-tekton.md)

diff --git a/...ersion-3.10/operator-guide/project-management-and-reporting/jira-integration.md b/...ersion-3.10/operator-guide/project-management-and-reporting/jira-integration.md
@@ -133,8 +133,6 @@ In order to adjust the Jira server integration, add the JiraServer CR by perform
       3. **Add Comments:** Required for adding external links and comments to issues.
     :::
 
-
-
 ## Enable Jira During Platform Deployment
 
 KubeRocketCI offers the capability to incorporate Jira integration as part of its deployment process. To follow this approach, please review the following parameters of the [values.yaml](https://github.com/epam/edp-install/blob/release/3.9/deploy-templates/values.yaml#L145) file. Enabling the `jira.integration` parameter creates the following custom resources:

diff --git a/versioned_docs/version-3.10/user-guide/components.md b/versioned_docs/version-3.10/user-guide/components.md
@@ -7,7 +7,6 @@ description: "Explore the essentials of codebases and onboarding strategies in K
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # Components: Codebases and Onboarding Strategies
 
 <head>

diff --git a/versioned_docs/version-3.10/user-guide/gitops.md b/versioned_docs/version-3.10/user-guide/gitops.md
@@ -7,7 +7,6 @@ sidebar_label: "Manage Clusters"
 ---
 <!-- markdownlint-disable MD025 -->
 
-
 # Manage GitOps
 
 <head>

diff --git a/versioned_docs/version-3.9/operator-guide/auth/configure-keycloak-oidc-eks.md b/versioned_docs/version-3.9/operator-guide/auth/configure-keycloak-oidc-eks.md
@@ -104,7 +104,6 @@ The initial step involves setting up the Keycloak operator (configure connection
       enable: true
     ```
 
-
 This add-ons facilitates sets up a broker realm to manage traffic redirection between external Identity Providers (IdP) and internal clients. Additionally, it creates a shared realm that encompasses all clients, including to EKS, Sonar, Nexus, and Portal.
 
 The [KubeRocketCI RBAC add-on](https://github.com/epam/edp-cluster-add-ons/tree/main/clusters/core/addons/kuberocketci-rbac) creates Keycloak groups that are used in the KubeRocketCI platform to manage access to resources. For more details refer to the [KubeRocketCI Groups](platform-auth-model.md#groups) documentation.

diff --git a/versioned_docs/version-3.9/operator-guide/cd/argocd-integration.md b/versioned_docs/version-3.9/operator-guide/cd/argocd-integration.md
@@ -302,7 +302,6 @@ This section provides the information on how to test the integration with Argo C
 
     </details>
 
-
 2. Check that your new Application is added to the Argo CD UI under the `edp` Project scope.
 
 ## Deploy Argo CD Application to Remote Cluster (Optional)

diff --git a/...version-3.9/operator-guide/project-management-and-reporting/jira-integration.md b/...version-3.9/operator-guide/project-management-and-reporting/jira-integration.md
@@ -133,8 +133,6 @@ In order to adjust the Jira server integration, add the JiraServer CR by perform
       3. **Add Comments:** Required for adding external links and comments to issues.
     :::
 
-
-
 ## Enable Jira During Platform Deployment
 
 KubeRocketCI offers the capability to incorporate Jira integration as part of its deployment process. To follow this approach, please review the following parameters of the [values.yaml](https://github.com/epam/edp-install/blob/release/3.9/deploy-templates/values.yaml#L145) file. Enabling the `jira.integration` parameter creates the following custom resources:
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,7 +5,6 @@ sidebar_label: "KubeRocketCI Reference Architecture on AWS" @@
     ---
     <!-- markdownlint-disable MD025 -->
     # KubeRocketCI Reference Architecture on AWS
     <head>
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
Expand Up		@@ -301,7 +301,6 @@ This section provides the information on how to test the integration with Argo C

		</details>


		2. Check that your new Application is added to the Argo CD UI under the `edp` Project scope.

		## Deploy Argo CD Application to Remote Cluster (Optional)
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -100,7 +100,6 @@ After the changes are applied, the tekton-pipelines metrics will be available in

		![Tekton dashboard](../../assets/operator-guide/grafana-dashboard-is-created.png "Tekton dashboard is created")


		## Related Articles

		* [Install Tekton](../install-tekton.md)
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -302,7 +302,6 @@ This section provides the information on how to test the integration with Argo C

		</details>


		2. Check that your new Application is added to the Argo CD UI under the `edp` Project scope.

		## Deploy Argo CD Application to Remote Cluster (Optional)
Expand Down