You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/started/k8s/kfctl-existing-arrikto.md
+7-69
Original file line number
Diff line number
Diff line change
@@ -1,73 +1,18 @@
1
1
+++
2
-
title = "Kubeflow on Kubernetes"
3
-
description = "Instructions for installing Kubeflow on your existing Kubernetes cluster"
2
+
title = "Kubeflow Deployment with kfctl_existing_arrikto"
3
+
description = "Instructions for installing Kubeflow with kfctl_existing_arrikto config"
4
4
weight = 4
5
5
+++
6
6
7
-
Follow these instructions if you want to install Kubeflow on an existing Kubernetes cluster.
7
+
This deployment uses [Dex](https://github.com/dexidp/dex) and [Istio](https://istio.io/) for vendor-neutral authentication.
8
8
9
-
If you are using a Kubernetes distribution or Cloud Provider which has specific instructions for installing Kubeflow we recommend following those instructions. Those instructions do additional Cloud specific setup to create a really great Kubeflow experience.
10
-
11
-
For installing Kubeflow on an existing Kubernetes Cluster, you can use one of the following options:
12
-
13
-
*[Kubeflow for Existing Clusters by Arrikto](#Kubeflow-for-Existing-Clusters---by-Arrikto)
14
-
15
-
## Kubeflow for Existing Clusters - by Arrikto
16
-
17
-
This installation of Kubeflow is maintained by [Arrikto](https://www.arrikto.com/), is geared towards existing Kubernetes clusters and does not depend on any cloud-specific feature.
18
-
19
-
In this reference architecture, we use [Dex](https://github.com/dexidp/dex) and [Istio](https://istio.io/) for vendor-neutral authentication.
1. Run the following commands to set up and deploy Kubeflow. The code below includes an optional command to add the binary `kfctl` to your path. If you don't add the binary to your path, you must use the full path to the `kfctl` binary each time you run it.
93
31
@@ -521,4 +459,4 @@ Your Kubeflow app directory contains the following files and directories:
521
459
UIs](/docs/other-guides/accessing-uis/), where you can manage various
522
460
aspects of your Kubeflow deployment.
523
461
* Run a [sample machine learning workflow](/docs/examples/resources/).
524
-
* Get started with [Kubeflow Pipelines](/docs/pipelines/pipelines-quickstart/)
462
+
* Get started with [Kubeflow Pipelines](/docs/pipelines/pipelines-quickstart/)
title = "Kubeflow Deployment with kfctl_k8s_istio"
3
+
description = "Instructions for installing Kubeflow on your existing Kubernetes cluster using kfctl_k8s_istio config"
4
+
weight = 2
5
+
+++
6
+
7
+
This config creates a vanilla deployment of Kubeflow with all its core components without any external dependencies. The deployment can be customized based on your environment needs.
8
+
9
+
**Maintainer and supporter: Kubeflow community**
10
+
11
+
### Deploy Kubeflow
12
+
13
+
Follow these steps to deploy Kubeflow:
14
+
15
+
1. Download a `kfctl` release from the [Kubeflow releases page](https://github.com/kubeflow/kubeflow/releases/) and unpack it:
16
+
17
+
```
18
+
tar -xvf kfctl_<release tag>_<platform>.tar.gz
19
+
```
20
+
21
+
1. Run the following commands to set up and deploy Kubeflow. The code below includes an optional command to add the binary `kfctl` to your path. If you don't add the binary to your path, you must use the full path to the `kfctl` binary each time you run it.
22
+
23
+
```bash
24
+
# Add kfctl to PATH, to make the kfctl binary easier to use.
25
+
export PATH=$PATH:"<path to kfctl>"
26
+
export KFAPP="<your choice of application directory name>"
27
+
# Installs istio by default. Comment out istio components in the config file to skip istio installation. See https://github.com/kubeflow/kubeflow/pull/3663
***${KFAPP}** - the _name_ of a directory where you want Kubeflow
37
+
configurations to be stored. This directory is created when you run
38
+
`kfctl init`. If you want a custom deployment name, specify that name here.
39
+
The value of this variable becomes the name of your deployment.
40
+
The value of this variable cannot be greater than 25 characters. It must
41
+
contain just the directory name, not the full path to the directory.
42
+
The content of this directory is described in the next section.
43
+
44
+
45
+
Check the resources deployed in namespace `kubeflow`:
46
+
47
+
```
48
+
kubectl -n kubeflow get all
49
+
50
+
```
51
+
52
+
### Access Kubeflow Dashboard
53
+
54
+
Once Kubeflow is deployed, the Kubeflow Dashboard can be accessed via `istio-ingressgateway` service. If loadbalancer is not available in your environment, NodePort or Port forwarding can be used to access the Kubeflow Dashboard.Refer [Ingress Gateway guide](https://istio.io/docs/tasks/traffic-management/ingress/ingress-control/).
55
+
56
+
### Delete Kubeflow
57
+
58
+
Run the following commands to delete your deployment and reclaim all resources:
59
+
60
+
```bash
61
+
cd${KFAPP}
62
+
# If you want to delete all the resources, run:
63
+
kfctl delete all -V
64
+
```
65
+
66
+
### Understanding the deployment process
67
+
68
+
The deployment process is controlled by 4 different commands:
69
+
70
+
***init** - one time set up.
71
+
***generate** - creates config files defining the various resources.
72
+
***apply** - creates or updates the resources.
73
+
***delete** - deletes the resources.
74
+
75
+
With the exception of `init`, all commands take an argument which describes the
76
+
set of resources to apply the command to; this argument can be one of the
77
+
following:
78
+
79
+
***k8s** - all resources that run on Kubernetes.
80
+
***all** - platform and Kubernetes resources.
81
+
82
+
#### App layout
83
+
84
+
Your Kubeflow app directory contains the following files and directories:
85
+
86
+
***${KFAPP}/app.yaml** defines configurations related to your Kubeflow deployment.
87
+
***${KFAPP}/kustomize**: contains the YAML manifests that will be deployed.
88
+
89
+
### Next steps
90
+
91
+
* Run a [sample machine learning workflow](/docs/examples/resources/).
92
+
* Get started with [Kubeflow Pipelines](/docs/pipelines/pipelines-quickstart/)
description = "Instructions for installing Kubeflow on your existing Kubernetes cluster with list of supported options"
4
+
weight = 1
5
+
+++
6
+
7
+
Follow these instructions if you want to install Kubeflow on an existing Kubernetes cluster.
8
+
9
+
If you are using a Kubernetes distribution or Cloud Provider which has specific instructions for installing Kubeflow we recommend following those instructions. Those instructions do additional Cloud specific setup to create a really great Kubeflow experience.
10
+
11
+
The following table lists the options for installing Kubeflow on an existing Kubernetes Cluster and links to detailed instructions.
12
+
13
+
### Community maintained
14
+
15
+
This section includes vendor-neutral solutions governed by community consensus. Below deployment configs are maintained and supported by the community.
16
+
17
+
<divclass="table-responsive">
18
+
<tableclass="table table-bordered">
19
+
<thead class="thead-light">
20
+
<tr>
21
+
<th>Deployment config</th>
22
+
<th>Description</th>
23
+
</tr>
24
+
</thead>
25
+
<tbody>
26
+
<tr>
27
+
<td>kfctl_k8s_istio.yaml</td>
28
+
<td> This config creates a vanilla deployment of Kubeflow with all its core components without any external dependencies. The deployment can be customized based on your environment needs. <br />Follow instructions: <a href="/docs/started/k8s/kfctl-k8s-istio/">Kubeflow Deployment with kfctl_k8s_istio</a></td>
29
+
</tr>
30
+
</tbody>
31
+
</table>
32
+
</div>
33
+
34
+
### Vendor maintained
35
+
36
+
This section includes the deployment solutions that are supported by specific vendors/providers.
37
+
38
+
<divclass="table-responsive">
39
+
<tableclass="table table-bordered">
40
+
<thead class="thead-light">
41
+
<tr>
42
+
<th>Deployment config</th>
43
+
<th>Description</th>
44
+
<th>Maintainer/Supporter</th>
45
+
</tr>
46
+
</thead>
47
+
<tbody>
48
+
<tr>
49
+
<td>existing_arrikto.yaml</td>
50
+
<td> This deployment uses Dex and Istio for vendor-neutral authentication. <br />Follow instructions: <a href="/docs/started/k8s/kfctl-existing-arrikto/">Kubeflow Deployment with existing_arrikto</a></td>
0 commit comments