diff --git a/modules/gitops-release-notes-1-10-0.adoc b/modules/gitops-release-notes-1-10-0.adoc index 136f8103ee46..f3f36ca142b2 100644 --- a/modules/gitops-release-notes-1-10-0.adoc +++ b/modules/gitops-release-notes-1-10-0.adoc @@ -40,7 +40,7 @@ The current release adds the following improvements: By default, the conversion webhook is enabled only for OLM-installed Operators. For non-OLM installations of the Operator, enabling the webhook is optional. However, without conversion webhook support, you have to manually migrate any existing Argo CD `v1alpha1` CRs to `v1beta1`. ==== -* With this update, the {gitops-title} Operator deploys three monitoring dashboards in the Administrator perspective of the web console. The three dashboards are *GitOps Overview*, *GitOps Components*, and *GitOps gRPC*. To access these dashboards, go to *Observe* → *Monitoring*. link:https:https://issues.redhat.com/browse/GITOPS-1767[GITOPS-1767] +* With this update, the {gitops-title} Operator deploys three monitoring dashboards in the Administrator perspective of the web console. The three dashboards are *GitOps Overview*, *GitOps Components*, and *GitOps gRPC*. To access these dashboards, go to *Observe* → *Monitoring*. link:https://issues.redhat.com/browse/GITOPS-1767[GITOPS-1767] + [NOTE] ==== diff --git a/observability/logging/viewing-argo-cd-logs.adoc b/observability/logging/viewing-argo-cd-logs.adoc index a00deb492268..2779c6f14075 100644 --- a/observability/logging/viewing-argo-cd-logs.adoc +++ b/observability/logging/viewing-argo-cd-logs.adoc @@ -14,4 +14,4 @@ include::modules/gitops-storing-and-retrieving-argo-cd-logs.adoc[leveloffset=+1] [role="_additional-resources"] [id="additional-resources_viewing-argo-cd-logs"] == Additional resources -* link:https://docs.openshift.com/container-platform/latest/logging/cluster-logging-deploying.html#cluster-logging-deploy-console_cluster-logging-deploying[Installing the {logging-title} using the web console] \ No newline at end of file +* link:https://docs.openshift.com/container-platform/latest/observability/logging/cluster-logging-deploying.html#cluster-logging-deploy-console_cluster-logging-deploying[Installing the {logging-title} using the web console] \ No newline at end of file diff --git a/observability/monitoring/monitoring-argo-cd-custom-resource-workloads.adoc b/observability/monitoring/monitoring-argo-cd-custom-resource-workloads.adoc index 761a0c669e57..3d37f5a14f62 100644 --- a/observability/monitoring/monitoring-argo-cd-custom-resource-workloads.adoc +++ b/observability/monitoring/monitoring-argo-cd-custom-resource-workloads.adoc @@ -17,8 +17,8 @@ You can enable and disable the setting for monitoring Argo CD custom resource wo * You have access to the cluster as a user with the `cluster-admin` role. * {gitops-title} is installed in your cluster. * The monitoring stack is configured in your cluster in the `openshift-monitoring` project. In addition, the Argo CD instance is in a namespace that you can monitor through Prometheus. -* The `kube-state-metrics` service is running in your cluster. -* Optional: If you are enabling monitoring for an Argo CD instance already present in a user-defined project, ensure that the monitoring is link:https://docs.openshift.com/container-platform/latest/monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[enabled for user-defined projects] in your cluster. +* The `kube-state-metrics` service is running on your cluster. +* Optional: If you are enabling monitoring for an Argo CD instance already present in a user-defined project, ensure that the monitoring is link:https://docs.openshift.com/container-platform/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[enabled for user-defined projects] in your cluster. + [NOTE] ==== @@ -34,4 +34,4 @@ include::modules/gitops-disabling-monitoring-for-argo-cd-custom-resource-workloa [role="_additional-resources"] [id="additional-resources_monitoring-argo-cd-custom-resource-workloads"] == Additional resources -* link:https://docs.openshift.com/container-platform/latest/monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects[Enabling monitoring for user-defined projects] +* link:https://docs.openshift.com/container-platform/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html#enabling-monitoring-for-user-defined-projects_enabling-monitoring-for-user-defined-projects[Enabling monitoring for user-defined projects] \ No newline at end of file diff --git a/securing_openshift_gitops/managing-secrets-securely-using-sscsid-with-gitops.adoc b/securing_openshift_gitops/managing-secrets-securely-using-sscsid-with-gitops.adoc index 3464c2a85e1b..a57bbec6cbdf 100644 --- a/securing_openshift_gitops/managing-secrets-securely-using-sscsid-with-gitops.adoc +++ b/securing_openshift_gitops/managing-secrets-securely-using-sscsid-with-gitops.adoc @@ -38,7 +38,8 @@ include::modules/gitops-configuring-gitops-managed-resources-to-use-mounted-secr == Additional resources * link:https://github.com/redhat-developer/gitops-operator/blob/bfdf81944ea60b1d62d7de7c223c3bea3e7363a6/docs/Integrate%20GitOps%20with%20Secrets%20Management.md#obtain-the-ccoctl-tool[Obtaining the `ccoctl` tool] -* link:https://docs.openshift.com/container-platform/latest/installing/installing_aws/installing-aws-customizations.html#cco-ccoctl-configuring_installing-aws-customizations[Configuring the Cloud Credential Operator utility] +* link:https://docs.openshift.com/container-platform/latest/authentication/managing_cloud_provider_credentials/about-cloud-credential-operator.html[About the Cloud Credential Operator] +* link:https://docs.openshift.com/container-platform/latest/authentication/managing_cloud_provider_credentials/about-cloud-credential-operator.html#cco-determine-mode_about-cloud-credential-operator[Determining the Cloud Credential Operator mode] * link:https://github.com/redhat-developer/gitops-operator/blob/bfdf81944ea60b1d62d7de7c223c3bea3e7363a6/docs/Integrate%20GitOps%20with%20Secrets%20Management.md#configure-your-aws-cluster-to-use-aws-security-token-service-sts[Configure your AWS cluster to use AWS STS] * link:https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html[Configuring AWS Secrets Manager to store the required secrets] * link:https://docs.openshift.com/container-platform/latest/nodes/pods/nodes-pods-secrets-store.html#persistent-storage-csi-secrets-store-driver-overview_nodes-pods-secrets-store[About the Secrets Store CSI Driver Operator]