Release Notes 2.3.2

DKP® version 2.3.2 was released on February 14, 2023

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 DKP.

Release Summary

Welcome to D2iQ Kubernetes Platform (DKP) 2.3.2! This release provides fixes to reported issues, integrates changes from previous releases, and maintains compatibility and support for other packages used in DKP.

DKP Fixes and Updates

The following issues are corrected or resolved in this release.

Kube-oidc-proxy is not Available After Upgrade

D2IQ-94629

If you installed or attached a cluster in 2.1, kube-oidc-proxy was not available after upgrading to 2.3.x. This prevented authentication via kubectl using SSO.

Failure to Upgrade Azure Clusters

D2IQ-95191

A bug in the Azure CSI driver caused problems during an upgrade by preventing volumes attached to cluster nodes from being detached, in some circumstances, so they were not available for the new nodes created by the upgrade process. This problem would prevent pods on the upgraded cluster from starting.

CAPA Provider for EKS not Working with -worker-iam-instance-profile

D2IQ-95493

When creating an EKS cluster and specifying a specific IAM instance profile to use on worker nodes, the nodes are created with the specified IAM instance profile. However, the CAPA controller currently does not honor this role, resulting in deployment failures. To workaround this issue, follow the instructions on the Grant Cluster Access page to adjust the roles the CAPA controller uses. In some instances, the IAM authenticator was missed as a prerequisite. For more information see the Amazon EKS documentation: Installing aws-iam-authenticator

AKS Cluster Deployment hangs in a Pending State

D2IQ-94072

When deploying an AKS cluster using the DKP UI on an Azure hosted Management cluster, the AKS cluster deployed correctly, but was staying in the Pending state when viewed from the UI.

Improved Documentation for Changing Calico Encapsulation Type

D2IQ-94582

While deploying DKP 2.3 to a pre-provisioned Azure cluster, the documentation for changing the encapsulation type was not correct, which prevented correct configuration of the Calico Overlay network.

Kommander Installations Fail in Certain Scenarios

D2IQ-92981

When deploying DKP Applications to a centos79 pre-provisioned, air-gapped, and FIPS environment, deployment was failing due to the gatekeeper-update-namespace-label pod crashing and looping.

Corrected Upgrade Documentation to Specify Correct Kubernetes version

D2IQ-93793

This upgrade path to use when upgrading to DKP 2.3 failed due to an incorrectly configured flag.

KIB 1.24.x Fails and Cannot Create Ubuntu Images

D2IQ-95429

Creating an Ubuntu 1804 or 2004 image for GCP with KIB 1.24.2 or 1.24.3 failed with an error.

DKP Insights Fixes and Updates

Incorrect CSI-related Polaris Messages for GCP and Azure

D2IQ-92665

DKP Insights was displaying some incorrect CSI-related critical Polaris messages for GCP and Azure clusters, but not AWS.

Download Signature Files

You need to download an appropriate, signed signature file before you run FIPS validation. Verify which version of DKP you are running to ensure you are downloading the manifest that is compliant with the DKP release number on your system. You can use the FIPS validation tool to verify that specific components and services are FIPS-compliant by checking the signatures of the files against a signed signature file, and by checking that services are using the certified algorithms. Select the links in the Manifest URL column of the following table to obtain a valid file: 

DKP version 2.3.2

Supported Versions

Any DKP cluster you attach using DKP 2.3.2 must be running a Kubernetes version in the following ranges:

DKP 2.3 comes with support for Kubernetes 1.23, enabling you to benefit from the latest features and security fixes in upstream Kubernetes. This release comes with approximately 47 enhancements. To read more about major features in this release, visit https://kubernetes.io/blog/2021/12/07/kubernetes-1-23-release-announcement/.

2.3.2 Components and Applications

The following are component and application versions for DKP 2.3.2:

Components

Applications

Known Issues and Limitations

The following items are known issues with this release.

Nvidia Feature Discovery Error

D2IQ-93676

When creating a new cluster to migrate Kaptain to version 2.1, after creating the cluster, the nvidia-feature-discovery-gpu-feature-discovery is in a CrashLoopBackOff state, with error.

Workaround

Follow these steps

1. Place the registry details in the override file, together with Nvidia.

2. Delete the current override and replaced it with the new override you just created in step 1.

3. Delete the machine to force preprovisioning.

4. Rename or delete the *.toml files from the import path directory set in config.toml

5. Restart containerd and GPU/Nvidia feature discovery.

6. Verify the Node now shows GPU resources.

7. Repeat these steps for all affected nodes.

Use static credentials to provision an Azure cluster

Only static credentials can be used when provisioning an Azure cluster.

When attaching GKE clusters, create a ResourceQuota to enable log collection

After you attach the GKE cluster, you can choose to deploy a stack of applications for workspace or project log collection. Once you have enabled this stack, create a ResourceQuota which is required for the logging stack to function correctly. You will have to do this manually, because some DKP versions do not properly handle this by default.
Create the following resource to enable log collection:

1. Execute the following command to get the namespace of your workspace on the management cluster:

   CODE

   kubectl get workspaces

   And copy the value under WORKSPACE NAMESPACE column for your workspace. This may NOT be identical to the Display Name of the Workspace.

2. Set the WORKSPACE_NAMESPACE environment variable to the name of the workspace’s namespace:

   CODE

   export WORKSPACE_NAMESPACE=<gkeattached-cluster-namespace>

3. Run the following command on your attached GKE cluster to create the resource:

   CODE

   cat << EOF | kubectl apply -f -
   apiVersion: v1
   kind: ResourceQuota
   metadata:
     name: fluent-bit-critical-pods
     namespace: ${WORKSPACE_NAMESPACE}
   spec:
     hard:
       pods: "1G"
     scopeSelector:
       matchExpressions:
       - operator: In
         scopeName: PriorityClass
         values:
         - system-node-critical
   EOF

After a few minutes, log collection is available in your GKE cluster.

This workflow only creates a ResourceQuota in the targeted workspace. Repeat these steps if you want to deploy the logging stack to additional workspaces with GKE clusters.

Resolve issues with failed HelmReleases

There is an existing issue with the Flux helm-controller that can cause HelmReleases to get "stuck" with an error message such as Helm upgrade failed: another operation (install/upgrade/rollback) is in progress. This can happen when the helm-controller is restarted while a HelmRelease is upgrading, installing, and so on.

Workaround

To ensure the HelmRelease error was caused by the helm-controller restarting, first try to suspend/resume the HelmRelease:

kubectl -n <namespace> patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": true}]'
kubectl -n <namespace> patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": false}]'

This might resolve the issue. If not, continue with the following steps:   

You should see the HelmRelease attempting to reconcile, and then it either succeeds (with status: 'Release reconciliation succeeded') or it fails with the same error as before. 

If the HelmRelease is still in the failed state, it is likely related to the helm-controller restarting. For example, if the 'reloader' HelmRelease is the one that is stuck.

To resolve the issue, follow these steps:

1. List secrets containing the affected HelmRelease name:

   CODE

   kubectl get secrets -n ${NAMESPACE} | grep reloader

   CODE

   kommander-reloader-reloader-token-9qd8b                        kubernetes.io/service-account-token   3      171m
   sh.helm.release.v1.kommander-reloader.v1                       helm.sh/release.v1                    1      171m
   sh.helm.release.v1.kommander-reloader.v2                       helm.sh/release.v1                    1      117m           

   In this example, sh.helm.release.v1.kommander-reloader.v2 is the most recent revision.

2. Find and delete the most recent revision secret. For example sh.helm.release.v1.*.<revision>

   CODE

   kubectl delete secret -n <namespace> <most recent helm revision secret name>

3. Suspend and resume the HelmRelease to trigger a reconciliation:

   CODE

   kubectl -n <namespace> patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": true}]'
   kubectl -n <namespace> patch helmrelease <HELMRELEASE_NAME> --type='json' -p='[{"op": "replace", "path": "/spec/suspend", "value": false}]'

You should see the HelmRelease is reconciled and eventually the upgrade and install succeeds.

Fluentbit disabled by default for DKP 2.3

Fluentbit is disabled by default in DKP 2.3 due to memory constraints. The amount of admin logs ingested to Loki requires additional disk space to be configured on the grafana-loki-minio Minio Tenant. Enabling admin logs may use around 2GB/day per node. See Configuring-the-Grafana-Loki-Minio-Tenant for more details on how to configure the Minio Tenant.

If Fluentbit is enabled on the management cluster and you would like it to continue to be deployed after the upgrade, you must pass in the --disable-appdeployments {} flag to the dkp upgrade kommander command. Otherwise, Fluentbit is automatically disabled upon upgrade.

Configure the Grafana Loki MinIO Tenant

Additional steps are required to change the default configuration of the MinIO Tenant that is deployed with Grafana Loki, grafana-loki-minio. Using config overrides is not supported.

By default, the grafana-loki-minio MinIO Tenant is configured with 2 pools with 4 servers each, 1 volume per server, for a total of 80GB.

The MinIO usable storage capacity is always less than the actual storage amount.

Use MinIO Erasure code calculator to establish the appropriate configuration for your log storage requirement.

• You are only able to expand MinIO storage by adding more MinIO server pools with the correct configuration. Modifying existing server pools does not work as MinIO does not support reducing storage capacity. See this MinIO Operator documentation for details.

• This impacts all your AppDeployment objects that reference the grafana-loki Kommander application definition.

• The changes introduced by the following procedure are wiped out upon Kommander install and upgrade.

In this example, we modify the grafana-loki-minio MinIO Tenant object in kommander-workspace (namespace: kommander)

1. Use this script to clone the management git repository from the Management cluster:

   CODE

   export KUBECONFIG=$KUBECONFIG
   
   PASS=$(kubectl get secrets -nkommander admin-git-credentials -oyaml -o go-template="{{.data.password | base64decode }}")
   URL=https://gitea_admin:$PASS@$(kubectl -n kommander get ingress gitea -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'):443/dkp/kommander/git/kommander/kommander
   
   git clone -c http.sslVerify=false $URL repo

2. Modify repo/services/grafana-loki/0.48.4/minio.yaml by appending a new server pool to .spec.pools field, for example:

   CODE

   # the following will add a new server pool with 4 servers
   # each server is attached with 1 PersistentVolume of 50G
   - servers: 4
     volumesPerServer: 1
     volumeClaimTemplate:
       metadata:
         name: grafana-loki-minio
       spec:
         accessModes:
           - ReadWriteOnce
         resources:
           requests:
             storage: 50Gi
     resources:
       limits:
         cpu: 750m
         memory: 1Gi
       requests:
         cpu: 250m
         memory: 768Mi
     securityContext:
       runAsUser: 0
       runAsGroup: 0
       runAsNonRoot: false
       fsGroup: 0

3. Commit the changes to local clone of the git management repository when you are done editing:

   CODE

   git add services/grafana-loki/0.48.4/minio.yaml
   git commit # finish the commit message editing in editor

4. Ensure that it is safe to apply the change, and then push the change to management git repository:

   CODE

   git push origin main

5. Set your WORKSPACE_NAMESPACE env variable:

   CODE

   # this is an example for kommander-workspace
   export WORKSPACE_NAMESPACE=kommander

6. Verify that the Tenant is modified as expected, when the grafana-loki kustomizations reconcile:

   CODE

   # this prints the .status field of the tenant
   kubectl get tenants -n kommander grafana-loki-minio -o jsonpath='{ .status }' | jq

7. Verify that the new StatefulSet is READY:

   CODE

   kubectl get sts -n $WORKSPACE_NAMESPACE -l v1.min.io/tenant=grafana-loki-minio
   
   NAME                      READY   AGE
   grafana-loki-minio-ss-0   4/4     144m
   grafana-loki-minio-ss-1   4/4     144m
   grafana-loki-minio-ss-2   4/4     15m

8. Restart all the StatefulSets that back this Tenant:

   CODE

   kubectl -n $WORKSPACE_NAMESPACE rollout restart sts grafana-loki-minio-ss-0
   statefulset.apps/grafana-loki-minio-ss-0 restarted
   kubectl -n $WORKSPACE_NAMESPACE rollout restart sts grafana-loki-minio-ss-1
   statefulset.apps/grafana-loki-minio-ss-1 restarted
   kubectl -n $WORKSPACE_NAMESPACE rollout restart sts grafana-loki-minio-ss-2
   statefulset.apps/grafana-loki-minio-ss-2 restarted

9. Verify that the MinIO Pods that back this Tenant are all online:

   CODE

   kubectl logs -n $WORKSPACE_NAMESPACE -l v1.min.io/tenant=grafana-loki-minio
   ...
   Verifying if 1 bucket is consistent across drives...
   Automatically configured API requests per node based on available memory on the system: 424
   All MinIO sub-systems initialized successfully
   Waiting for all MinIO IAM sub-system to be initialized.. lock acquired
   Status:         12 Online, 0 Offline. 
   API: http://minio.kommander.svc.cluster.local 
   
   Console: http://192.168.202.223:9090 http://127.0.0.1:9090   
   
   Documentation: https://docs.min.io
   ...

FIPS upgrade from 2.2.x to 2.3.0

If upgrading a FIPS cluster, there is a bug in the upgrade of kube-proxy DaemonSet in that it does not get automatically upgraded. After completing the cluster upgrade, run the following command to finish upgrading the kube-proxy DaemonSet:

kubectl set image -n kube-system daemonset.v1.apps/kube-proxy kube-proxy=docker.io/mesosphere/kube-proxy:v1.23.12_fips.0

Additional resources

• For more information about working with native Kubernetes, see the Kubernetes documentation.

• For a full list of attributed 3rd party software, see http://d2iq.com/legal/3rd.