Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Troubleshoot Helm Controller alerts

This section describes the investigation and troubleshooting steps for the Helm Controller service and the HelmBundle custom resources.

• HelmBundleReleaseNotDeployed

• HelmControllerReconcileDown

• HelmControllerTargetDown

---

HelmBundleReleaseNotDeployed

Root cause	Helm Controller release status differs from deployed. Broken HelmBundle configurations or missing Helm chart artifacts may cause this when applying the HelmBundle update.
Investigation	Inspect logs of every Helm Controller Pod for error or warning messages: kubectl logs -n <controller_namespace> <controller_name> In case of an error to fetch the chart, review the chartURL fields of the HelmBundle object to verify that the chart URL does not have typographical errors: kubectl get helmbundle -n <helmbundle_namespace> <helmbundle_name> -o yaml Verify that the chart artifact is accessible from your cluster.
Mitigation	If the chart artifact is not accessible from your cluster, investigate the network-related alerts, if any, and verify that the file is available in the repository.

See also

Collect cluster logs

HelmControllerReconcileDown

Root cause	Helm Controller failed to reconcile the HelmBundle spec.
Investigation and mitigation	Refer to HelmBundleReleaseNotDeployed.

HelmControllerTargetDown

Root cause

Prometheus fails in at least 10% of Helm Controller metrics scrapes. The following two components can cause the alert to fire: Helm Controller Pod(s): If the Pod is down. If the Pod target endpoint is at least partially unresponsive. For example, in case of CPU throttling, application error preventing a restart, or container flapping. Prometheus server if it cannot reach the helm-controller endpoint(s).

Investigation and mitigation

Refer to KubePodsCrashLooping. Inspect and resolve the network-related alerts.