csoceanu · csoceanu · Jul 10, 2025 · Jul 10, 2025 · Jul 17, 2025 · Jul 17, 2025
diff --git a/modules/ROOT/pages/getting-started.adoc b/modules/ROOT/pages/getting-started.adoc
@@ -156,4 +156,4 @@ include::partial${context}-additional-getting-started.adoc[]
 
 == Getting started with the CLI
 
-include::partial${context}-getting-started-with-the-cli.adoc[]
+include::partial${context}-getting-started-with-the-cli.adoc[]
diff --git a/modules/building/pages/configuration-as-code.adoc b/modules/building/pages/configuration-as-code.adoc
@@ -319,4 +319,4 @@ If you follow this method to create an `application-b` composed of `component-c`
 
 NOTE: You can also modify the project structure to fit your own needs by moving application bases and component definitions to different levels, but this configuration offers the most layered encapsulation across applications and application versions.
 
-IMPORTANT: Managing multiple related components and applications can be challenging. Refer https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/proc_multiversion/ [Managing multiple software versions] to manage multiple related components and applications.
+IMPORTANT: Managing multiple related components and applications can be challenging. Refer https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/proc_multiversion/ [Managing multiple software versions] to manage multiple related components and applications.
diff --git a/modules/building/pages/creating-secrets.adoc b/modules/building/pages/creating-secrets.adoc
@@ -45,8 +45,8 @@ Some container builds may use parent images from registries that require authent
 
 . Obtain the username and password login credentials for the container registry.
     * For access to `registry.redhat.io`, you can create a registry service account at https://access.redhat.com/terms-based-registry/accounts.
-. In the correct {ProductName} tenant namespace, go to **Secrets**. 
-. Click **Add secret**.  
+. In the correct {ProductName} tenant namespace, go to **Secrets**.
+. Click **Add secret**.
 . For **Secret type**, select **Image pull secret**.
 . For **Authentication type**, select **Image registry credentials**.
 . For **Registry server address** enter the image registry (for example `registry.redhat.io`).
@@ -77,11 +77,11 @@ Here is the YAML representation of the secret (for reference):
 ----
 apiVersion: v1
 data:
-.dockerconfigjson: <base64-encoded-credentials>
+  .dockerconfigjson: <base64-encoded-credentials>
 kind: Secret
 metadata:
-name: my-quay-secret
-namespace: <your-tenant>
+  name: my-quay-secret
+  namespace: <your-tenant>
 type: kubernetes.io/dockerconfigjson
 ----
 
@@ -277,4 +277,4 @@ include::partial${context}-secrets-external-vault.adoc[]
 
 * For more information about GitLab access tokens, see link:https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html[Project access tokens].
 
-* To configure push secrets for your Build and Release pipelines, see link:https://github.com/konflux-ci/konflux-ci?tab=readme-ov-file#configuring-a-push-secret-for-the-build-pipeline[Configuring push secrets] in the Konflux GitHub repository.
+* To configure push secrets for your Build and Release pipelines, see link:https://github.com/konflux-ci/konflux-ci?tab=readme-ov-file#configuring-a-push-secret-for-the-build-pipeline[Configuring push secrets] in the Konflux GitHub repository.
diff --git a/modules/building/pages/index.adoc b/modules/building/pages/index.adoc
@@ -2,8 +2,16 @@
 
 When creating a component, {ProductName} will push a Tekton PipelineRun to your component's source repository. This pipeline is yours to customize as needed for building your component and Tekton Chains will record the customizations in a detailed signed in-toto provenance attestation. This provenance enables Conforma to xref:compliance:index.adoc[manage compliance] to ensure the artifact's integrity and compliance with specific policies.
 
+== Automated Documentation Updates
+
+{ProductName} leverages an automated documentation update mechanism that responds to specific comments on Pull Requests. This system uses the `docs-enhancer.yml` workflow to automatically update documentation whenever a pull request comment contains `[update-docs]`.
+
+This automation ensures that documentation remains current with code changes, streamlining the process of maintaining accurate and comprehensive project information.
+
 == Additional resources [[additional-resources]]
 
 * The sample pipelines that you can initially configure your components with depend on the {ProductName} deployment. This might include the pipelines provided by xref:installing:enabling-builds.adoc#available-pipelines[{ProductName}] or other additional pipelines.
 * If you want to change the configured pipeline for your component after it is onboarded, see xref:building:reconfiguring-build-pipeline.adoc#changing-pipelines[reconfiguring the build pipeline].
 * Since the Tekton PipelineRuns use link:https://pipelinesascode.com[Pipelines as Code] to trigger the jobs on the cluster, you can also use any of the link:https://pipelinesascode.com/docs/guide/authoringprs/#default-parameters[default parameters] in the PipelineRuns in your git repositories.
+* The `kube-linter.yaml`, `pr.yaml`, and `codecov-main.yaml` GitHub workflows have been removed. This means the project no longer automatically checks Kubernetes YAMLs with `kube-linter` on pull requests, performs `golangci-lint`, `gosec` security scans, or `envtest` runs on pull requests, and no longer generates `codecov` reports on pushes to the `main` branch.
+* The `config/default/kustomization.yaml` has been updated to include enhanced monitoring and webhook support, with standardized labeling (`app.kubernetes.io/name`, `app.kubernetes.io/component`, `monitoring`) and enabled network policies.
diff --git a/modules/end-to-end/pages/building-tekton-tasks.adoc b/modules/end-to-end/pages/building-tekton-tasks.adoc
@@ -260,4 +260,4 @@ spec:
 After completing all the steps above we should now have:
 
 * A task release as a bundle in our release repository
-* An OCI artifact named *data-acceptable-bundles* in our release repository, containing a SHA reference of the latest task release as a trusted task (all the previous versions of the task will appear with the expires_on parameter)
+* An OCI artifact named *data-acceptable-bundles* in our release repository, containing a SHA reference of the latest task release as a trusted task (all the previous versions of the task will appear with the expires_on parameter)
diff --git a/modules/installing/nav.adoc b/modules/installing/nav.adoc
@@ -1,4 +1,6 @@
 ** Installation
 *** xref:index.adoc[Installing {ProductName}]
 *** xref:enabling-builds.adoc[Enabling build pipelines]
-*** xref:github-app.adoc[GitHub App]
+*** xref:github-app.adoc[GitHub App]
+*** xref:docs-automation.adoc[Documentation Automation]
+*** xref:kustomization-config.adoc[Kustomization Configuration]
diff --git a/modules/installing/pages/enabling-builds.adoc b/modules/installing/pages/enabling-builds.adoc
@@ -39,7 +39,7 @@ This **ConfigMap** can contain references to any Tekton pipeline bundles. Additi
 In order to support different use cases within {ProductName}, multiple Tekton pipeline bundles are available in the `quay.io/konflux-ci` organization.
 
 NOTE: The tasks included in the pipeline definitions can be discovered using `yq` or `jq`. For example,
-```bash
+----
 $ tkn bundle list -o yaml quay.io/konflux-ci/tekton-catalog/pipeline-docker-build:devel pipeline docker-build 2>/dev/null | yq ".spec.tasks.[].name"
 init
 clone-repository
@@ -54,7 +54,7 @@ sast-snyk-check
 clamav-scan
 apply-tags
 push-dockerfile
-```
+----
 
 ==== _docker-build_ [[docker-build]]
 

diff --git a/modules/installing/pages/index.adoc b/modules/installing/pages/index.adoc
@@ -8,4 +8,16 @@ Before tapping into the vast array of benefits offered by {ProductName}, the ini
 
 . *Using Kubernetes manifests*: This option supports any image registry and involves fewer initial setup steps.
 
-For detailed instructions, refer to the link:https://github.com/konflux-ci/konflux-ci/blob/main/README.md[installation guide].
+For detailed instructions, refer to the link:https://github.com/konflux-ci/konflux-ci/blob/main/README.md[installation guide].
+
+Additionally, {ProductName} now includes enhanced documentation automation. This feature automatically updates documentation based on code changes by commenting `[update-docs]` on a Pull Request. This ensures that the documentation always reflects the latest state of the codebase, improving accuracy and reducing manual effort.
+
+[[enhanced-observability]]
+==== Enhanced Observability
+
+This update introduces enhanced monitoring, webhook support, and network policies for better observability and security within {ProductName}.
+
+* *Monitoring*: Enabled standardized labeling for resource identification and monitoring, ensuring that pods running in namespaces labeled `metrics: enabled` can gather metrics.
+* *Webhook Server*: The webhook server is now enabled for validation and mutation purposes. CRs that require webhooks and are applied on namespaces labeled `webhooks: enabled` can communicate with the webhook server.
+* *Certificate Manager*: The certificate manager is enabled for automated TLS certificate management, which is required by webhook components.
+* *Network Policies*: Network policies are enabled to enhance the security posture of the deployment.
diff --git a/modules/patterns/pages/gitops-for-manual-releases.adoc b/modules/patterns/pages/gitops-for-manual-releases.adoc
@@ -89,7 +89,7 @@ Let's say you're preparing for an upcoming 1.3.0 release.
 ----
 ❯ yq -i '.metadata.name = "your-project-1-3-0-rc01"' releases/1.3.0/snapshot.yaml
 # Confirm the name is as you expect
-❯ yq .metadata.name releases/1.3.0/snapshot.yaml                                 
+❯ yq .metadata.name releases/1.3.0/snapshot.yaml
 your-project-1-3-0-rc01
 ----
 
@@ -122,4 +122,4 @@ NOTE: Discuss this with your team. The decision depends on your process outside
 [source]
 ----
 ❯ watch 'kubectl get releases your-project-1-3-0 -o yaml | yq .status'`
-----
+----
diff --git a/modules/patterns/pages/maintaining-references-before-release.adoc b/modules/patterns/pages/maintaining-references-before-release.adoc
@@ -44,4 +44,4 @@ NOTE: Once this change is merged, the nudged component will contain invalid refe
 .*Verification*
 
 . Commit a change to a nudging component, triggering a push event.
-. After the build is completed, a pull request should be opened against your nudged component's git repository.
+. After the build is completed, a pull request should be opened against your nudged component's git repository.
diff --git a/modules/patterns/pages/testing-releasing-single-component.adoc b/modules/patterns/pages/testing-releasing-single-component.adoc
@@ -107,4 +107,4 @@ reduce-snapshot
 [reduce] SNAPSHOT_CREATION_COMPONENT: comp2
 [reduce] Single Component mode is true and Snapshot type is component
 [reduce] COMPONENT_COUNT: 1
---
+--
diff --git a/modules/reference/nav.adoc b/modules/reference/nav.adoc
@@ -14,4 +14,4 @@
 *** xref:kube-apis/mintmaker.adoc#k8s-api-github-com-konflux-ci-release-service-api-v1alpha1-dependencyupdatecheck[DependencyUpdateCheck]
 *** xref:kube-apis/project-controller.adoc#k8s-api-github-com-konflux-ci-project-controller-api-v1beta1-project[Project]
 *** xref:kube-apis/project-controller.adoc#k8s-api-github-com-konflux-ci-project-controller-api-v1beta1-projectdevelopmentstream[ProjectDevelopmentStream]
-*** xref:kube-apis/project-controller.adoc#k8s-api-github-com-konflux-ci-project-controller-api-v1beta1-projectdevelopmentstreamtemplate[ProjectDevelopmentStreamTemplate]
+*** xref:kube-apis/project-controller.adoc#k8s-api-github-com-konflux-ci-project-controller-api-v1beta1-projectdevelopmentstreamtemplate[ProjectDevelopmentStreamTemplate]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -156,4 +156,4 @@ include::partial${context}-additional-getting-started.adoc[]

		== Getting started with the CLI

		include::partial${context}-getting-started-with-the-cli.adoc[]
		include::partial${context}-getting-started-with-the-cli.adoc[]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -319,4 +319,4 @@ If you follow this method to create an `application-b` composed of `component-c`

		NOTE: You can also modify the project structure to fit your own needs by moving application bases and component definitions to different levels, but this configuration offers the most layered encapsulation across applications and application versions.

		IMPORTANT: Managing multiple related components and applications can be challenging. Refer https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/proc_multiversion/ [Managing multiple software versions] to manage multiple related components and applications.
		IMPORTANT: Managing multiple related components and applications can be challenging. Refer https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/proc_multiversion/ [Managing multiple software versions] to manage multiple related components and applications.