Welcome to the Deploy Charmed Kubeflow to EKS guide. This how-to guide will take you through the steps of deploying Kubeflow to an AWS Elastic Kubernetes Service (EKS) cluster. From an architectural point of view, we will spin up an EKS cluster on AWS cloud using eksctl
on our local machine. Then with kubectl
and juju
still on our local machine, we will interact with the cluster to deploy Kubeflow there.
Requirements:
- Local machine with Ubuntu 22.04 or later
- An AWS account (How to create an AWS account)
Content
Deploy EKS cluster
See here for a complete guide on how to do exactly that.
Set up Juju
Set upjuju
on your local machine to access the remote Kubernetes cloud.
-
Install
juju
. Normally, you would install juju usingsnap
. For the use with EKS though, install Juju from binary using the latest3.4.x
package for your machine. This is becauseJuju 3.4
cannot add public clouds when installed from snap (juju bug) due to strict confinement of the snap. -
Add your EKS cluster as a cloud to Juju (
kubeflow
cloud name is optional).
juju add-k8s kubeflow --client
- Bootstrap a Juju controller (
kubeflow-controller
controller’s name is optional).
juju bootstrap kubeflow kubeflow-controller
- Add a Juju model (
kubeflow
name here is mandatory).
juju add-model kubeflow
- Verify that namespace
kubeflow
exists
kubectl get ns
Deploy Kubeflow bundle
- Deploy Charmed Kubeflow bundle with the following command.
juju deploy kubeflow --channel=1.8/stable --trust
- Wait until all charms are in green/active state. You can check the state of the charms with the following command. In case you face any issues, refer to the Known issues section below. Keep in mind that
oidc-gatekeeper
will go toBlocked
status until we configure it as shown in next steps.
juju status --watch 5s --relations
- Make Kubeflow dashboard accessible by configuring its public URL to be the same as the LoadBalancer’s DNS record.
PUBLIC_URL="http://$(kubectl -n kubeflow get svc istio-ingressgateway-workload -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')"
echo PUBLIC_URL: $PUBLIC_URL
juju config dex-auth public-url=$PUBLIC_URL
juju config oidc-gatekeeper public-url=$PUBLIC_URL
- Configure Dex-auth credentials. Feel free to use a different (more secure!) password if you wish.
juju config dex-auth static-username=user@example.com
juju config dex-auth static-password=user
- Navigate to the PUBLIC_URL printed above to access Kubeflow dashboard. You should first see the Dex login screen. Once logged in with the credentials set above, you should now see the Kubeflow “Welcome” page.
Known issues
Oidc-gatekeeper “Waiting for pod startup to complete”
If you see the oidc-gatekeeper/0
unit in juju status
output in waiting state with
oidc-gatekeeper/0* waiting idle 10.1.121.241 Waiting for pod startup to complete.
You can reconfigure the public-url configuration for the charm with following commands
PUBLIC_URL="http://$(kubectl -n kubeflow get svc istio-ingressgateway-workload -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')"
juju config oidc-gatekeeper public-url=""
juju config oidc-gatekeeper public-url=$PUBLIC_URL
Clean up resources
For EKS clean up, refer to the guide mentioned here. In order to clean up juju, run the following:
juju unregister kubeflow-controller
juju remove-cloud kubeflow --client