NKP 2.13.0 Customer Incidents and Resolved Issues

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

No Input Field to Specify the Azure Image Name While Provisioning Clusters

Fixed an issue where an input field to specify the Azure image names was not available while provisioning an NKP cluster through the UI using the Azure infrastructure provider.

NCN-104022

Configuring the Certificate results in an Error Message

Fixed an issue where configuring a certificate while adding an infrastructure provider displayed an error message.

NCN-104050

NKP Edit Command Does Not Work as Expected

Fixed an issue where while creating an a new catalog gitrepository, the nkp edit command provided by the NKP CLI does not work as expected.

NCN-104112

Preflight Checks Are Not Run During the NKP Kommander Installation

Fixed an issue where the preflight checks were not run during the NKP Kommander installation for attached or managed clusters.

NCN-104332

Grafana Loki Compaction Does Not Work with the Default Configuration

Fixed an issue where the Grafana Loki compaction did not work with the default configuration.

NCN-104281

Scaling the Nodepool Using MachineDeployment Scales a Different Cluster

Fixed an issue where scaling a nodepool using MachineDeployment scaled the nodepool in a different cluster instead.

NCN-104294

The ai-navigator-cluster-info-api Pods Fail

Fixed an issue where the ai-navigator-cluster-info-api pods failed.

NCN-104260

Cannot Deploy a Cluster with the Name Containing a Dot(.) using the Starter License

Fixed an issue where a workload cluster name containing a dot (.) could not be created using the Starter license.

NCN-102869

Kommander "cluster" Flux Kustomization is in an Unhealthy State after Kommander Upgrade

Fixed an issue where the Kommander "cluster" Flux Kustomization was in an unhealthy state after performing a Kommander upgrade.

NCN-104389

MetalLB Configuration for the vSphere or Preprovisioned Cluster Upgrade

When you upgrade a vSphere or Preprovisioned cluster, you run the upgrade addons command. This migrates your MetalLB configuration from a ConfigMap to one or more Custom Resources defined by MetalLB. The Custom Resources are created in the metallb-system namespace. Although the version of MetalLB included in NKP no longer uses the ConfigMap, the ConfigMap will not be deleted. However, you may delete the ConfigMap post-install.

NCN-103615