NKP 2.13.1 Known Issues and Limitations
The following items are known issues with this release:
Rook Ceph Install Error
An issue might emerge when installing rook-ceph
on vSphere clusters using RHEL operating systems.
This issue occurs during initial installation of rook-ceph
, causing the object store used by Velero and Grafana Loki, to be unavailable. If the installation of Kommander component of DKP 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
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 configuration requires that the ACME server is able to reach the Ingress IP address through the configured DNS record. If your cluster is not accessible from the internet, then then HTTP-01 configuration is not possible for the public ACME services.
Workaround: You can provide the ACME configuration for DNS-01 resolver that works with the private IP addresses after the cluster is provisioned.
NCN-102071
Custom Banner on Cluster is lost during an upgrade
If you used the ‘Custom Banner’ UI functionality in a previous version of NKP/DKP and then Upgrade to NKP 2.13, the Banner is lost during the upgrade and will need to be recreated.
NCN-100842