Release Summary

D2iQ is announcing Kaptain 2.1 which includes several user experience features, additional platforms supported, and resolves reported issues. This continues our tradition of customer-led development making Kaptain even easier to deploy, supporting more platforms, and incorporating the latest innovations from the open source community in the hot AI/ML marketplace. Kaptain 2.1 supports Kubeflow 1.5 and a new version of the Kaptain SDK, 1.0.1. For more information on SDK 1.0.1, see SDK release notes.

New features and capabilities

Support of MLflow

You can use the MLflow platform with Kaptain to collect data and manage the lifecycle of your Machine Learning and Artificial Intelligence models and experiments. You can now log hyperparameters and metrics to the MLflow instance that is bundled with Kaptain. For more information on how MLflow is integrated to Kaptain and how to use it, refer to the MLflow documentation.

Restrict access to Kaptain by establishing a list of allowed groups

You can authenticate and enable users and user groups to access Kaptain by linking your Kaptain’s Dex instance to an identity provider of your choice. From this release on, you have the option of adding or removing groups (that are established in your identity provider) to the AllowList to further restrict access to your Kaptain instance.

Fixes and Improvements

Software updates

Known issues

cert-manager workaround for Kaptain

Some Kommander versions do not properly handle certificate renewal for the Cluster CA and certificates that are created for Kommander applications, which also affects Kaptain. While the effects can vary, the most common failure is the inability to launch Kaptain notebooks in Jupyter.

Regenerate the secrets in DKP

A permanent fix for the issue requires upgrading to Kommander 2.2.1 or higher. If you are running other versions of DKP, refer to the cert-manager expiration workaround documentation for DKP 2.1.0, 2.1.1 or 2.1.2 to run a docker container that extends the validity of the Cluster CA to 10 years and fixes the certificate reload issue.

Once this is done, you can fix the issue on Kaptain’s side.

Regain access to Kaptain

This gives you back the capability of launching notebooks in Jupyter:

Kaptain has one certificate that you have to delete to force a refresh, and one that you can update manually for Istio:
```
kubectl delete secrets kubeflow-gateway-certs -n kaptain-ingress --force
```

Obtain the CA from one of the other recreated certs:

kubectl get secret kommander-traefik-certificate -n kommander -o jsonpath='{.data.ca\.crt}' > ca.crt

Use this CA and apply it to the Istio CA:

kubectl delete secret kubeflow-oidc-ca-bundle -n kaptain-ingress --force
kubectl -n kaptain-ingress create secret generic kubeflow-oidc-ca-bundle --from-file=oidcCABundle\.crt=ca.crt

Running this command reloads the pod automatically. Wait a few minutes until you attempt to log in to DKP and Kaptain again.

Test by logging into both and launch a new notebook in Jupyter.

Release Notes for Kaptain 2.1.0

View release-specific information for Kaptain