.png)
NKP 2.14.0 Known Issues and Limitations
The following items are known issues with this release:
Harbor UI Displays Unlimited Quota for Storage Providers
When Harbor is deployed for a storage provider, the Harbor UI incorrectly displays Quota used: X MiB of Unlimited on the dashboard even though the storage provider has pre-configured limits set based on the configured Persistent Volume (PV).
NCN-105785
PVCs Cause the Pods to Get Stuck During Kommander Installation
During the Kommander installation, Persistent Volume Claims (PVCs) restrict the associated pods, preventing successful installation. This issue occurs when the PVC is not provisioned properly, leading to the pod failing to start.
NCN-105557
Unable to Deploy User Applications on Management Cluster Using NCR Private Registry
Deploying user applications on the Management cluster using the NCR Private Registry fails with the following error: "tls: failed to verify certificate: x509: certificate signed by unknown authority".
This issue occurs due to a mismatch or invalid certificate, leading to the failure of image pulls from the private registry.
NCN-105471
Rook Ceph Install Error
An issue might emerge when installing rook-ceph on vSphere clusters using RHEL operating systems.
This issue occurs during the initial installation of rook-ceph, causing the object store used by Velero and Grafana Loki to be unavailable. If the installation of the DKP Kommander component is unsuccessful due to rook-ceph failing, you might need to apply a workaround. For more information, see Troubleshooting the Rook Ceph Install Error.
NCN-104559
Custom Banner on Cluster is Lost During an Upgrade
If you use the ‘Custom Banner’ UI functionality in a previous version of NKP and then upgrade to NKP 2.14, the Banner is lost during the upgrade and must be recreated. NCN-100842
Unable to create a cluster using the RHCK kernel
When creating a new cluster using Oracle Linux 7.9 with the RHCK kernel, the cluster appears ready and begins to pivot but fails, resulting in an error. NCN-102061
Unable to deploy Kommander in TUI
Using the ACME configuration results in a cert-manager ClusterIssuer created on the newly provisioned cluster with the provided values and HTTP-01 solver configuration for default Ingress. The HTTP-01 configuration requires that the ACME server be able to reach the Ingress IP address through the configured DNS record. If your cluster is not accessible from the internet, then the HTTP-01 configuration is not possible for public ACME services.
Workaround: You can provide the ACME configuration for the DNS-01 resolver that works with the private IP addresses after the cluster is provisioned.
NCN-102071
NKP 2.14 Limitations
Image Registry Usages in NKP Workload Clusters
Due to limitations in the NKP UI and CLI, you can configure a Workload cluster only with a single set of cluster-wide image registry credentials. A Workload cluster deployment in a non-air-gapped environment attempts to pull images from Docker Hub. Due to Docker Hub's image pull rate limits, you are required to provide the Docker Hub credentials.
Also, if you create a Management cluster without providing a trusted CA certificate, then the NCR private registry is accessible only over HTTPS with a self-signed certificate. To pull images from the NCR registry successfully, you must configure new Workload clusters with the same self-signed certificate.
Workaround:
To use both Docker Hub credentials and the NCR registry certificate, use the --dry-run workflow and update the cluster object. For more information, see https://nutanix-cloud-native.github.io/cluster-api-runtime-extensions-nutanix/customization/generic/image-registries/ .
If you create the Management cluster with a trusted CA certificate, then you can specify the NCR registry credentials using the image pull secrets. For more information, see https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ .
NCN-105470
Harbor Support on FIPS Clusters
NKP 2.14 does not support Harbor on FIPS clusters.
NCN-105816