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

Trusting NCR Private Registry's CA Certificate

When creating a Management cluster with default configuration without using a trusted CA certificate as described in Configuring the Kommander Installation with a Custom Domain and Certificate, the deployed NCR registry is only accessible over HTTPS with a self-signed certificate.

Workaround: To use the NCR registry in a workload cluster, you must configure it to trust the self-signed certificate. For instructions, see Using Integrated Private Registry on an NKP Cluster.

NCN-105470

Harbor Support on FIPS Clusters

NKP 2.14 does not support Harbor on FIPS clusters.

NCN-105816