NKP 2.15.1 is a maintenance release focused on stability, security, and smoother day-to-day operations.

What’s New

• Bitnami Image Migration Resolved
  We’ve eliminated the dependency on Bitnami’s public catalog after their migration, ensuring images are consistently available without disruption.

Fixes and Improvements

• Harbor UI Quota Display
  Storage provider quotas may still incorrectly appear as “Unlimited” in the Harbor UI, but configured limits remain enforced.

• Private Registry Deployments
  Applications deployed on the management cluster using the NCR private registry may fail due to certificate mismatches. A trusted CA configuration is recommended.

• Kommander Installation Reliability
  Certain persistent volume claims (PVCs) may prevent Kommander installation. Restarting the pod allows installation to continue.

• Rook Ceph on vSphere
  Some RHEL-based vSphere clusters may encounter errors when deploying Rook Ceph, impacting Velero and Loki object stores.

• Custom Cluster Banners
  Custom banners created on earlier versions are lost during upgrades and must be reapplied.

• UI Refresh Needed
  During cluster creation, UI options may dim until the page is refreshed.

Limitations & Deprecations

• Air-gapped Trivy Scans
  Vulnerability scans require a manual database sync in air-gapped environments.

• Harbor on FIPS
  Harbor is not supported on FIPS clusters.

• Self-Signed Certificates
  By default, the NCR registry uses self-signed certificates. Workload clusters must be configured to trust these.

• OS & API Changes

  • Ubuntu 20.04 support removed.

  • RHEL 8.8 deprecated.

  • apps.kommander.mesosphere.io/v1alpha2 API is deprecated in favor of v1alpha3.

  • The --charts-bundle flag is no longer required for Kommander installation.