Kubeflow
- By Kubeflow Charmers | bundle
- Cloud
Channel | Revision | Published |
---|---|---|
latest/stable | 414 | 01 Dec 2023 |
latest/candidate | 294 | 24 Jan 2022 |
latest/beta | 430 | 30 Aug 2024 |
latest/edge | 423 | 26 Jul 2024 |
1.9/stable | 426 | 31 Jul 2024 |
1.9/beta | 420 | 19 Jul 2024 |
1.9/edge | 425 | 31 Jul 2024 |
1.8/stable | 414 | 22 Nov 2023 |
1.8/beta | 411 | 22 Nov 2023 |
1.8/edge | 413 | 22 Nov 2023 |
1.7/stable | 409 | 27 Oct 2023 |
1.7/beta | 408 | 27 Oct 2023 |
1.7/edge | 407 | 27 Oct 2023 |
1.6/stable | 329 | 07 Sep 2022 |
1.6/beta | 326 | 23 Aug 2022 |
1.6/edge | 328 | 07 Sep 2022 |
1.4/stable | 321 | 30 Jun 2022 |
1.4/edge | 320 | 30 Jun 2022 |
juju deploy kubeflow --channel edge
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
In Charmed Kubeflow, object storage access can be achieved with MinIO. Access via MinIO requires some special configuration. It is relevant for local workstations as well as private cloud deployments.
See more: Charmhub | MinIO
Contents:
- Configure the keys for MinIO
- Create the “allow-minio.yaml” file
- Configure the “allow-minio.yaml” file
- Refresh Juju
Configure the keys for MinIO
First, check if the access key is configured:
juju config minio access-key
Then, check if the secret key is configured:
juju config minio secret-key
In case they are set, please remember the set credentials. Otherwise, please go ahead and set a new username and password:
juju config minio access-key=<username>
juju config minio secret-key=<password>
Please bear in mind that both username and password need to have a minimum of 8 characters.
See also: Juju OLM |
juju config
, Charmhub >minio
> Configure
Create the “allow-minio.yaml” file
In order to gain access to MinIO, it has to be added to the pod and configured. In order to do that, a YAML needs to be created and configured.
In the terminal, please run: touch allow-minio.yaml
.
After that, please run: nano allow-minio.yaml
.
Configure the “allow-minio.yaml” file
Once the “allow-minio.yaml” file opens, please update the information within it as below:apiVersion: kubeflow.org/v1alpha1
kind: PodDefault
metadata:
name: access-minio
spec:
desc: Allow access to Minio
selector:
matchLabels:
access-minio: "true"
env:
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: mlpipeline-minio-artifact
key: accesskey
optional: false
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: mlpipeline-minio-artifact
key: secretkey
optional: false
- name: MINIO_ENDPOINT_URL
value: http://minio.kubeflow.svc.cluster.local:9000
Please save it and then close it.
After that, please run in the terminal the following command:
kubectl apply -f allow-minio.yaml -n <user-namespace>
Refresh Juju
In the terminal please runjuju refresh –kubeflow
.
After that, you should be able to access Minio. If you would like to check if it is added to the model, please run it in the terminal.
sudo microk8s kubectl get PodDefault -n admin
There you should see “allow-minio”
.
Another option is to access the MinIO dashboard. By doing this you need to run juju status
and take the IP address of MinIO <>. Go to your browser, where you already set up the Proxy for Kubeflow and enter it. In order to login, please use the username and password that you previously set.