DKP 2.7.0 Customer Incidents and Resolved Issues

The following resolved incidents are fixed or corrected in this release.

Upgrading Expansion for Essential Cluster to Managed fails to take ownership of Cert-manager

Since Cert-manager is not managed by the Kommander component of DKP in an Essential cluster, you previously had to change the ownership of the Cert-manager application to Kommander ownership during the platform expansion process. This issue has been resolved.

D2IQ-99406

Gatekeeper is deployed to attached clusters even when it is disabled

After disabling Gatekeeper in a Workspace, Gatekeeper continued to be deployed to newly attached clusters in a Workspace. This issue was resolved.

D2IQ-97260 Incident

D2IQ-97301 Bug

Gatekeeper job will not be scheduled if the nodes have too many pods

When trying to install Kommander on a cluster that is fully loaded with lower priority pods, the Gatekeeper install step will fail. This issue was resolved by upgrading the apps to use version 3.13.0 of Gatekeeper.

D2IQ-97623

Kommander upgrade is successful even if Prometheus pods are still in a pending state

When upgrading Kommander, the kube-prometheus HelmRelease would show as healthy even if some of the Prometheus pods were still pending due to missing node capacity. This problem has been corrected.

D2IQ-94596