Skip to main content
Skip table of contents

NKP 2.12.1 Known Issues and Limitations

The following items are known issues with this release:

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 a 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 requires that the ACME server is able to reach the Ingress IP address through the configured DNS record. This is not possible for the public ACME services such as,"Let's Encrypt when using Nutanix the private IP addresses."

The ACME configuration for DNS-01 resolver that works with the private IP addresses can be provided after the cluster is provisioned.

NCN-102071

Issue with vSphere and Ubuntu using Konvoy Image Builder

Building a Konvoy Image Builder (KIB) image on vSphere using Ubuntu 20.04 with cloud-init 23.3.3-0ubuntu0~20.04.1 fails in all 2.12.x versions of NKP. The issue will be resolved in an upcoming KIB patch release.

NCN-102002

The cluster-autoscaler Deployment Must Exist in the Same Namespace as the Cluster it References

Running nkp move capi-resources --to-namespace=... with a different namespace for Nutanix clusters is not supported.

NCN-102055

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.