Release Notes Kommander 1.3.0

View release-specific information for Kommander 1.3.0

D2iQ® Kommander® version 1.3.0 was released on February 10, 2021.

To get started with Kommander, download and install the latest version of Konvoy.

NOTE: You must be a registered user and logged on to the support portal to download this product. New customers must contact their sales representative or sales@d2iq.com before attempting to download or install Konvoy.

Release Summary

Kommander provides a command center for all your cloud native management needs in public Information as a Service (IaaS), on-premises, and edge environments. Kommander provides a multi-tenant experience to create, secure, and configure Kubernetes clusters and cloud native workloads. Additionally, Kommander enables teams to unlock federated cost management across multiple clusters, whether they are a new Konvoy cluster or an existing 3rd party/DIY distribution installation.

Supported Versions

Kubernetes Support Version
Minimum 1.17.0
Maximum 1.19.x
Default 1.19.7

Known issues

In Kommander 1.3.2 and earlier versions, the Kubecost cost analyzer requests a PVC of size 0.2Gi by default. This can cause issues with provisioners requiring a minimum storage size of 1Gi. Upgrade to version 1.3.3 to resolve this issue. Refer here for more information.

In Kommander 1.3, unless a default NetworkPolicy existed prior to upgrading to 1.3, a default NetworkPolicy is created that allows traffic originating only within your Projects namespace. Pods can not talk to Pods outside of that namespace. In some cases this can have an unpredictable and unwanted impact on your system.

An alternative is to create an allow-all NetworkPolicy for each project in each managed cluster. Refer to following steps:

  1. Point kubectl to the managed cluster

  2. Enter the following command:

    cat <<EOF | kubectl apply -f -
      apiVersion: networking.k8s.io/v1
      kind: NetworkPolicy
      metadata:
        name: allow-all
        namespace: <namespace corresponding to the project>
     spec:
       ingress:
       - {}
       podSelector: {}
       policyTypes:
       - Ingress
     EOF
    
  3. Repeat steps 1 & 2 for each project namespace and managed cluster.

Breaking changes

Docker hub rate limiting

Docker Hub announced an update to their image pull policies in August, 2020. The change results in the need to change cluster configurations to accommodate new account structures that enable image pull rate limiting.

Rate limiting happens on a per-pull basis regardless of whether the pulled image is owned by a paid user. This means D2iQ, as owner of most images used in Konvoy, does not have any influence as to whether your current address is rate-limited or not. Konvoy does not have a strict dependency on Docker Hub accounts or plans.

For more information on addressing this limit, see Docker hub rate limits.

New Features

Control and configure workspace platform services

Customers now have the ability to control and configure which platform services get installed into an attached cluster by workspace. In Kommander specific platform services can be federated to attached non-Konvoy clusters. In each workspace customers can specify which platform services are federated to the attached non-Konvoy clusters.

For more information, see Workspace Platform Services.

Managed cluster multi-tenancy

Kommander now supports managing network policies across project clusters. Projects are created with a secure-by-default network policy and users needing more flexibility can edit or add more policies to tailor to their unique security needs.

For more information, see Network Policies.

Continuous deployment using Dispatch on Kommander

Kommander now supports continuous deployments as part of projects. Teams can leverage GitOps best practices to deploy configurations from source repositories to managed clusters using Dispatch and FluxCD. You can also configure source repositories to be deployed across all managed clusters using GitOps best practices. Kommander uses Dispatch and FluxCD to enable continuous deployments as a standard feature of projects.

For more information, see Continuous Deployments.

Component versions

  • Addon: 1.3.0-6
  • Chart: 0.13.7
  • kommander-federation (yakcl): 0.7.0
  • kommander-licensing (yakcl): 0.7.0
  • UI: 6.70.0
  • kommander-karma: 0.3.12
  • kubeaddons-catalog: 0.1.15
  • kommander-thanos: 0.1.16
  • kubecost: 0.1.15
  • grafana: 6.6.0
  • karma: 0.70
  • thanos: 0.10.1
  • cost-analyzer: 1.70.1

Fixed and Improved Issues

  • Added Kubecost Prometheus health dashboards to Grafana.
  • Added the ability to edit network policies.
  • Fixed Limit Range memory.
  • Numerous UX bug fixes and improvements.