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: proposals/649-kubeflow-helm-support/README.MD
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ By making deployment easy, we attract more end users and foster collaboration wi
37
37
38
38
39
39
## Non-Goals
40
-
* Deep integration with hyperscalers such as S3 object storage (basic Dex/oauth2-proxy config is valid).
40
+
* Deep integration with hyperscalers such as AWS managed databases. Nevertheless for example basic Dex/oauth2-proxy configuration for authentication integration with popular Kubernetes platforms such as EKS is a goal, because it is needed for M2M authentication within Kubeflow.
41
41
* Infrastructure provisioning. Users can opt into OpenTofu or Crossplane to template the Helm chart with infrastructure. Still, we are focused on the Helm chart where the values would be configured (if a component requires knowledge of external systems).
42
42
* Support separate abstracted operators for components. Helm will handle upgrades.
0 commit comments