DKP 2.8.0 Known Issues and Limitations
The following items are known issues with this release.
AWS Custom AMI Required for Kubernetes Version
Previous versions of DKP would default to using upstream AMIs published by the CAPA (Cluster API AWS) project when building AWS clusters if you did not specify your own AMI. However, those images are not currently available for the Kubernetes version used in the 2.8.0 release.
As a result, starting with this release of DKP, the behavior of the DKP create cluster aws
command has been changed. It no longer defaults to using the upstream AMIs and instead requires that you specify an AMI built using Konvoy Image Builder (KIB), or by explicitly requesting that it use the upstream images.
For more information on using a custom AMI in cluster creation or during the upgrade process, refer to these topics:
vSphere and Ubuntu using Konvoy Image Builder Issue
Building a Konvoy Image Builder (KIB) image on vSphere using Ubuntu 20.04 with cloud-init 23.3.3-0ubuntu0~20.04.1
will fail in the 2.8.0 version of DKP. The issue will be resolved in an upcoming KIB patch release.
Known CVE's
Since the release of DKP 2.6, DKP has been scanning Catalog applications for CVEs. Beginning with DKP 2.7, only the latest version of each Catalog application will be scanned (and have its critical CVEs mitigated). ` For more information about the known CVE’s for compatible catalog apps, refer to D2iQ Security Updates.
Custom Banner on Cluster will not Save on Upgrade from DKP 2.7.0 to 2.8.0, if you have a custom banner it will no longer be available in the UI. You can then create a new banner.