Overview
Users can understand the clusters in which their applications are deployed and manage and execute them using automation processes. Each component is implemented as a micro-service and operates in a Kubernetes cluster.
Container Cluster Management solution features the following key capabilities:
Production systems monitoring on Kubernetes and OpenShift clusters.
Visibility of logs in production without critical access.
Target personas include the following:
Alvin:
Site Reliability Engineer
Maureen:
Application Developer
Summary of features
Tool providers and open ecosystems have made fast progress in providing development and operational teams with supporting tools. IT generally requires numerous fit-for-purpose Kubernetes or OpenShift clusters to enable continuous integration/delivery (CI/CD) of different project pipelines as application workloads shift from development to production. The Console supports the following list of key features:
Production systems monitoring on Kubernetes and OpenShift clusters.
Visibility of logs in production without critical access
Container Cluster Management Dashboards
Container Cluster Management comprehensively explores your managed clusters across diverse cloud providers using Container Cluster Management. Navigate through the essential dashboard, a pivotal component featuring three widgets and a table view. The
Alerts
section provides an overview of alerts by cluster name and severity, with a detailed Alerts page accessible through cluster name links. The donut chart visualizes Cluster health by providers, distinguishing between healthy (green) and unhealthy (red) clusters. The Geomap widget offers insights into Cluster health by region based on global location. Explore the
Actionable Insights
widget for real-time data on running containers and resource utilization. Details about each cluster can be found in the Clusters table, covering names, connections, providers, locations, health, alerts, and Kubernetes or OpenShift versions.
CCM Integration with Applications
When a user chooses a particular cluster name on the Common Inventory Landing page (Resources page) and clicks the Container Cluster Management's consumer link, the Container Cluster Management system presents the cluster information and supplementary details via the Container Cluster Management details menu. The user can then return to the Common Inventory using the UI navigation by selecting the
"Back to Inventory"
link option.
Container Cluster Management Integration with DevOps Intelligence
You can access the cluster for a specific deployment within Kyndryl DevOps Intelligence by selecting its row within the Deployments table; additionally, by selecting the overflow menu on a deployment that has a cluster data point associated, the option
Go to CCM
will allow you to navigate directly to the Pods Namespace of that specific deployment and its details within the Container Cluster Management application; you will be redirected to the DevOps Intelligence application if you select
Back to DevOps Intelligence.
Every App must set the session storage and pass the query parameters accordingly to enable integration with Container Cluster Management.
Query parameters:
appId - It is a mandatory query parameter and should be the same as the session storage key.
appPage - is an optional query parameter and should be used in case of multiple navigations to Container Cluster Management UI from different pages within the same application
namespace - is an optional query parameter and can be used to set the namespace filter.
Session storage should be set by the application integrating with Container Cluster Management.
"breadCrumbItems" is an array of objects containing the text and the URL of the link to be part of the breadcrumb.
"backToLink" is an object containing the text and URL of the link linked to the Back link to the application.
"includeClusterLink" is set to true if the cluster name is to be displayed as a link to the overview page.
User access management
The Container Cluster Management Application needs to grant IAM access to users so they can elicit data within the platform while ensuring the appropriate management of authorized access to the platform resources.
This page reviews the basic procedures to grant access as needed, allowing visibility of the correct data to appropriate users within the Container Cluster Management Application.
As a Container Cluster Management Administrator, you can manage your Platform by inviting users and assigning specific policies based on their functions; you can add, edit, or delete users and their respective policies.
When a user accesses the Container Cluster Management dashboard and sees a
No Data Available
the message, two actions can be taken to pull data to the console:
Action 1:
Container Cluster Management and the cloud provider(s) are appropriately configured. If the configuration is valid, you should contact another user with the Base Operator or Base Editor role to validate the Cluster connection for that specific tenant. Please refer to Inviting Users for more details.
Action 2:
The user must check that the proper access group or policies for Container Cluster Management have been assigned; this can be done by selecting the Main menu and navigating to the portal; at the top left corner, the available roles will be presented. Suppose you have the Viewer role assigned. In that case, another user with a Base Operator or Base Editor position should be notified so that the proper role may be assigned.
Prerequisites:
Container Cluster Management Platform role: Administrator or Editor.