The Red Hat OpenShift GitOps Environments page in the Developer perspective of the OpenShift Container Platform web console shows a list of the successful deployments of the application environments, along with links to the revision for each deployment.
The Application environments page in the Developer perspective of the OpenShift Container Platform web console displays the health status of the application resources, such as routes, synchronization status, deployment configuration, and deployment history.
The environments pages in the Developer perspective of the OpenShift Container Platform web console are decoupled from the Red Hat OpenShift GitOps Application Manager command-line interface (CLI),
kam. You do not have to use
kam to generate Application Environment manifests for the environments to show up in the Developer perspective of the OpenShift Container Platform web console. You can use your own manifests, but the environments must still be represented by namespaces. In addition, specific labels and annotations are still needed.
The Red Hat OpenShift GitOps Operator will install the GitOps backend service in the
The Red Hat OpenShift GitOps Operator is installed from OperatorHub.
Ensure that your applications are synchronized by Argo CD.
Click Environments under the Developer perspective. The Environments page shows the list of applications along with their Environment status.
Hover over the icons under the Environment status column to see the synchronization status of all the environments.
Click on the application name from the list to view the details of a specific application.
In the Application environments page, if the Resources section under the Overview tab displays icons, hover over the icons to get status details.
A broken heart indicates that resource issues have degraded the application’s performance.
A yellow yield sign indicates that resource issues have delayed data about the application’s health.