DKP 2.7.1 Customer Incidents and Resolved Issues
The following resolved incidents are fixed or corrected in this release.
AI Navigator Pods Did Not have a Set PriorityClassName
D2IQ-100289
With the current 2.7.1 patch release, the AI Navigator components will have a priorityClassName set upon provisioning or upgrade.
CAPA AMIs are Not Available for the Kubernetes Version used in DKP 2.7.1
D2IQ-100175
AWS AMIs for some Kubernetes versions may not be available. We recommend using Konvoy Image Builder (KIB) to create a custom AMI.
Do not use the upstream values as defaults for the
--ami-*flags.If you specify any of these flags for AMI ID lookup, specify all of them:
--ami-base-os,--ami-format, and--ami-owner.
CAPI Move Causes Worker kubelet Issue in a Pre-provisioned Environment
D2IQ-97212
After performing dkp move capi-resources in a Pre-provisioned environment to make a cluster self-managed, one worker node experiences a not ready condition. The issue did not affect the other worker nodes, and was able to be corrected by deleting the machine associated with that node causing CAPI to re-provision the node. This issue has been resolved.