D2iQ® Kommander® version 2.2.1 was released on June 1, 2022.
Release summary
Welcome to D2iQ Kubernetes Platform (DKP) 2.2.1! This release provides fixes to reported issues, integrates changes from previous releases, and maintains compatibility and support for other packages used in DKP.
For this release, we are maintaining the documentation sets for individual platform components Konvoy and Kommander, while publishing some combined DKP documentation for processes, such as Upgrading DKP version.
DKP 2.2.x supports Kubernetes versions between 1.21.0 and 1.22.x. Any cluster you want to attach using DKP 2.2.x must be running a Kubernetes version in this range.
Supported versions
Kubernetes Support | Version |
---|---|
Minimum | 1.21.0 |
Maximum | 1.22.x |
Default | 1.22.0 |
Fixes and Improvements
ClusterResourceSet deployments create an unbounded number of service-account-tokens (COPS-7267)
An issue with the ClusterResourceSet controller in 2.2.0 causes an unbounded number of service account tokens to be created for each ClusterResourceSet. This problem has been corrected. A remediation is also available to identify and remove the excess secrets; see this knowledge base article for more information.
Certs showing as updated but not reloading in Kommander pods (COPS-7212)
Previous Kommander 2.x versions did not properly handle certificate renewal for the Cluster CA and the certificates that are created for Kommander applications. When the certificates expired, some Kommander applications and pods failed to receive the renewed certificate information, causing them to stop working upon expiration. This problem has been corrected.
kube-oidc-proxy error: certificate signed by unknown authority (COPS-7217)
When adding a new Attached Cluster to the Management Cluster, using a custom domain and TLS certificate issued by Let’s Encrypt, the kube-oidc-proxy helm chart in the Attached Cluster did not complete installation and the associated pod returned an error.
DKP Insights: Resource requests and limits are now configurable
You can now configure CPU and memory requests to use limits for the Insights management and backend components.
Other changes and capabilities
Flatcar
New preprovisioned clusters that use flatcar as a base operating system now use containerd
as the container runtime. You can update Preprovisioned clusters created with a previous version of dkp
to use containerd
runtime with this release.
Component updates
When upgrading to this release, the following services and service components are upgraded to the listed version:
Common Application Name | APP ID | Version | Component Versions |
---|---|---|---|
Cert Manager | cert-manager | 1.7.1 | - chart: 1.7.1 - cert-manager: 1.7.1 |
Chartmuseum | chartmuseum | 3.6.2 | - chart: 3.6.2 - chartmuseum: 3.6.2 |
Containerd | containerd | 1.4.11 | |
Dex | dex | 2.9.15 | - chart: 2.9.15 - dex: 2.22.0 |
External DNS | external-dns | 6.2.7 | - chart: 6.2.7 - external-dns: 0.11.0 |
Fluent Bit | fluent-bit | 0.19.20 | - chart: 0.19.20 - fluent-bit: 1.8.13 |
Flux | kommander-flux | 0.27.4 | |
Gatekeeper | gatekeeper | 3.7.0 | - chart: 3.7.0 - gatekeeper: 3.7.0 |
Grafana | grafana-logging | 6.22.0 | - chart: 6.22.0 - grafana: 8.3.6 |
Loki | grafana-loki | 0.33.2 | - chart: 0.33.1 - loki: 2.2.1 |
Istio | istio | 1.11.6 | - chart: 1.11.6 - istio: 1.11.5 |
Jaeger | jaeger | 2.29.0 | - chart: 2.29.0 - jaeger: 1.31.0 |
Karma | karma | 2.0.1 | - chart: 2.0.1 - karma: 0.88 |
Kiali | kiali | 1.47.0 | - chart: 1.47.0 - kiali: 1.47.0 |
Knative | knative | 0.3.9 | - chart: 0.3.9 - knative: 0.22.3 |
Kube OIDC Proxy | kube-oidc-proxy | 0.3.1 | - chart: 0.3.1 - kube-oidc-proxy: 0.3.0 |
Kube Prometheus Stack | kube-prometheus-stack | 33.1.6 | - chart: 33.1.6 - prometheus-operator: 0.54.1 - prometheus: 2.33.4 - prometheus alertmanager: 0.23.0 - grafana: 8.3.6 |
Kubecost | kubecost | 0.23.3 | - chart: 0.23.3 - cost-analyzer: 1.91.2 |
Kubefed | kubefed | 0.9.2 | - chart: 0.9.2 - kubefed: 0.9.1 |
Kubernetes Dashboard | kubernetes-dashboard | 5.1.1 | - chart: 5.1.1 - kubernetes-dashboard: 2.4.0 |
Kubetunnel | kubetunnel | 0.0.11 | - chart: 0.0.11 - kubetunnel: 0.0.11 |
Logging Operator | logging-operator | 3.17.2 | - chart: 3.17.2 - logging-operator: 3.17.2 |
Minio | minio-operator | 4.4.10 | - chart: 4.4.10 - minio: 4.4.10 |
NFS Server Provisioner | nfs-server-provisioner | 0.6.0 | - chart: 0.6.0 - nfs-provisioner: 2.3.0 |
Nvidia | nvidia | 0.4.4 | - chart: 0.4.4 - nvidia-device-plugin: 0.9.0 |
Grafana (project) | project-grafana-logging | 6.20.6 | - chart: 6.20.6 - grafana: 8.3.6 |
Loki (project) | project-grafana-loki | 0.33.2 | - chart: 0.33.1 - loki: 2.2.1 |
project-logging | 1.0.0 | ||
Prometheus Adapter | prometheus-adapter | 2.17.1 | - chart: 2.17.1 - prometheus-adapter: 0.9.1 |
Reloader | reloader | 0.0.104 | - chart: 0.0.104 - reloader: 0.0.104 |
Thanos | thanos | 0.4.6 | - chart: 0.4.6 - thanos: 0.9.0 |
Traefik | traefik | 10.9.1 | - chart: 10.9.1 - traefik: 2.5.6 |
Traefik ForwardAuth | traefik-forward-auth | 0.3.6 | - chart: 0.3.6 - traefik-forward-auth: 3.1.0 |
Velero | velero | 3.1.5 | - chart: 3.1.5 - velero: 1.5.2 |
Known Issues
The following items are known issues with this release.
Upgrade considerations
Before attempting to upgrade an existing cluster to this release, check the kommander-vars
Configmap in the kommander
namespace for the following fields:
- kommanderAppManagementImageTag
- kommanderAppManagementImageRepository
- kommanderChartsVersion
If any of the these fields are present, the upgrade can fail. If you encounter this situation, contact D2iQ Support for advice on how to remediate the issue before attempting to continue the upgrade.
Minio Disk insufficient space when upgrading
When upgrading DKP from v2.1.x to v2.2.x, the upgrade can fail due to insufficient space on the MinIO Disk. To avoid this issue, we recommend that you disable the fluent-bit
Platform Application before upgrading.
Additional resources
For more information about working with native Kubernetes, see the Kubernetes documentation.
For a full list of attributed 3rd party software, see d2iq.com/legal/3rd.