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
There are multiple config files available, each for a specific use case (e.g. GCP with IAP, GCP with basic auth, existing k8s with Istio, existing k8s with arrikto).
The URI for each config file changes with Kubeflow version, and may even change within a version.
Each URI is potentially used in more than one doc.
For the above reasons, it makes sense to specify the URIs in Hugo shortcodes so that (a) it's easy to find all the URIs as they're not scattered around various pages, and (b) we can be sure all docs are using the same config file for a particular use case.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.78. Please mark this comment with 👍 or 👎 to give our bot feedback!
When installing Kubeflow via the CLI, users need to specify a URI of a config file in
--config
argument.Example:
kfctl init ${KFAPP} --project=${PROJECT} --config="https://raw.githubusercontent.com/kubeflow/kubeflow/c54401e/bootstrap/config/kfctl_gcp_iap.0.6.2.yaml" -V
For the above reasons, it makes sense to specify the URIs in Hugo shortcodes so that (a) it's easy to find all the URIs as they're not scattered around various pages, and (b) we can be sure all docs are using the same config file for a particular use case.
The text was updated successfully, but these errors were encountered: