Product Advisory
| Advisory ID: | D2IQ-2020-0002 |
|---|---|
| Severity: | High |
| Synopsis: | Kernel kmem leak |
| Affected Products & Versions |
Konvoy 1.3.x |
| Issue date: | 03-06-2020 |
| Updated on: | 03-06-2020 (Initial Advisory) |
Background and Trigger
The Konvoy 1.4.0 release includes the latest version of Kommander which became generally available in February. In that release D2iQ changed the format of kubernetes-base-addons (kba) tags. This new tag format breaks versions of Konvoy 1.3 which include the pre-GA release of Kommander 1.0. The Kommander addon is on by default in Konvoy 1.3.x so unless the user turns it off, it will break the Konvoy deployment.Context and Symptoms
The Kubernetes addons - e.g. Kibana, Grafana, etc- will not be deployed in Konvoy 1.3.x.Mitigation and Workarounds
Kommander Users - If you need Kommander, then you must use Konvoy 1.4.x.If you have an existing Konvoy cluster with Kommander running, you need to update the cluster.yaml with the new kba tag and the new Kommander add-on repo. To do this please download Konvoy 1.4, run Konvoy init and then compare with the new 1.4.0 cluster.yaml. There is an example in the release notes: https://docs.d2iq.com/ksphere/konvoy/latest/release-notes/#version-v140-released-28-february-2020.
Once you have updated the cluster.yaml, run konvoy up to apply and upgrade Kommander.
New Konvoy Users - You should use Konvoy 1.4. If you are using Konvoy 1.3 then make sure that Kommander is turned off in the cluster.yaml.