Cloud Services

Container Cluster Management

Container Cluster Management release notes
Published On Jun 11, 2024 - 8:15 AM

Container Cluster Management release notes

Container Cluster Management provides the following support
On this page:
June 12th
  • Pods in CrashLoopBackOff: CrashLoopBackOff is a Kubernetes status indicating that a pod is failing to run successfully. CCM now identifies Pods in a CrashLoopBackOff status and provides root cause and recommendations to repair the underlying issue.
  • Pods restarted: CCM provides insights on the pods that were restarted in the last 24 hours and provides the root cause and recommendations. Pods in pending state: CCM identifies pods that are in a pending state with root cause and recommendations for remediation.
  • Pods with pending state: Shows the list of Pods which are in pending state.
  • Pods with Singleton design: CCM identifies pods that are designed to run as a single instance.
April 4th
  • Perform Day 2 actions in private container cluster: CCM now supports creation and deletion of namespaces and resources across Private Container Cluster.
  • Reskin of CCM Dashboard: The CCM dashboard got updated to match Shidoka.
  • Enable Actions from CCM: CCM being a common service in Kyndryl Bridge has enabled its support for creation and deletion of namespaces and resource across all major hyperscalers.
February 8th
Amazon CloudWatch now supported: Users benefit from real-time visibility into their cloud platform to facilitate troubleshooting, ensure availability and minimize impact on business operations.

Known issues

To access the latest known issues, see: Container Cluster Management known issues
Do you have two minutes for a quick survey?
Take Survey