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: README.md
+32-12Lines changed: 32 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ You can also install the master branch of [`kubeflow/manifests`](https://github.
10
10
11
11
We are planning to cut 2 releases per year, for example 26.03 and 26.10 before each KubeCon EU and NA.
12
12
We ask each working group/component to provide non-breaking patch releases for 6 months based on the version in each date release.
13
-
We try to BEST-EFFORT support each release for 6 months as community. There is [commercial support](https://www.kubeflow.org/docs/started/support/#support-from-commercial-providers-in-the-kubeflow-ecosystem) available if needed.
13
+
We try to BEST-EFFORT support each realease for 6 monhts as community. There is [commercial support](https://www.kubeflow.org/docs/started/support/#support-from-commercial-providers-in-the-kubeflow-ecosystem) available if needed.
14
14
The working groups (KFP, Katib, Trainer, ...) are allowed to release new component versions with breaking changes, but they will only be included in the master branch or the next date release.
15
15
This should only apply to “stable” components, as “alpha/beta” components might release breaking changes in patch releases.
16
16
@@ -63,7 +63,7 @@ This repository periodically synchronizes all official Kubeflow components from
63
63
| Component | Local Manifests Path | Upstream Revision | CPU (millicores) | Memory (Mi) | PVC Storage (GB) |
@@ -108,11 +109,6 @@ The `example` directory contains an example kustomization for the single command
108
109
- Our Kind script below will take care of installing continuously tested Kubernetes, Kustomize and Kubectl versions for you.
109
110
- We use Kind as default but also support Minikube, Rancher, EKS, AKS, and GKE. GKE might need tiny adjustments documented here in this file and OpenShift is also possible.
110
111
111
-
### ARM64 / aarch64 note
112
-
113
-
Kubeflow on ARM64/aarch64 may not be fully supported yet because some OCI images might not be available for `linux/arm64`.
114
-
If you hit image pull errors such as “no matching manifest for linux/arm64”, please track/report details in kubeflow/manifests#2745 and take a look at the [Google Summer of Code project for Kubeflow on ARM64](https://www.kubeflow.org/events/upcoming-events/gsoc-2026/#project--end-to-end-arm64-support--validation-on-kubeflow).
115
-
116
112
---
117
113
**NOTE**
118
114
@@ -182,6 +178,22 @@ Install the Kubeflow namespace:
This component provides an optional monitoring stack for GPU metrics (NVIDIA/AMD) and energy consumption (Kepler), along with Grafana dashboards. It includes Prometheus and Grafana operators and is deployed in the `kubeflow-monitoring-system` namespace.
The oauth2-proxy extends your Istio Ingress-Gateway capabilities to function as an OIDC client. It supports user sessions as well as proper token-based machine-to-machine authentication. Authorization which is completely different from authentication is handled via Kubernetes RBAC and Istio authorizationpolicies.
222
+
The oauth2-proxy extends your Istio Ingress-Gateway capabilities to function as an OIDC client. It supports user sessions as well as proper token-based machine-to-machine authentication. Authorization which is completely different form authentication is handled via Kubernetes RBAC and Istio authorizationpolicies.
Install the Model Registry with its UI and database components:
468
+
469
+
```sh
470
+
./tests/model_registry_install.sh
471
+
```
472
+
453
473
#### User Namespaces
454
474
455
475
Finally, create a new namespace for the default user (named `kubeflow-user-example-com`).
@@ -584,7 +604,7 @@ For modifications and in-place upgrades of the Kubeflow platform, we provide a r
584
604
585
605
To view all past security scans, head to the [Image Extracting and Security Scanning GitHub Action workflow](https://github.com/kubeflow/manifests/actions/workflows/trivy.yaml). In the logs of the workflow, you can expand the `Run image extracting and security scanning script` step to view the CVE logs. You will find a per-image CVE scan and a JSON dump of per-WorkingGroup aggregated metrics. You can run the Python script from the workflow file locally on your machine to obtain the detailed JSON files for any git commit.
586
606
587
-
For more information please consult the [SECURITY.md](./SECURITY.md).
607
+
For more infromation please consult the [SECURITY.md](./SECURITY.md).
588
608
589
609
## Pre-commit Hooks
590
610
@@ -624,7 +644,7 @@ pre-commit run
624
644
- **Q:** What versions of Istio, Knative, Cert-Manager, Argo, ... are compatible with Kubeflow?
625
645
**A:** Please refer to each individual component's documentation for a dependency compatibility range. For Istio, Knative, Dex, Cert-Manager, and OAuth2 Proxy, the versions in `common` are the ones we have validated.
626
646
- **Q:** Can I use Kubeflow in an air-gapped environment?
627
-
**A:** Yes you can. You just need to get the list of images from our [trivy CVE scanning script](https://github.com/kubeflow/manifests/blob/master/tests/trivy_scan.py), mirror them and replace the references in the manifests with kustomize components and overlays, see [Upgrading and Extending](#upgrading-and-extending). You could also use a simple kyverno policy to replace the images at runtime, which could be easier to maintain.
647
+
**A:** Yes you can. You just need to to get the list of images from our [trivy CVE scanning script](https://github.com/kubeflow/manifests/blob/master/tests/trivy_scan.py), mirror them and replace the references in the manifests with kustomize components and overlays, see [Upgrading and Extending](#upgrading-and-extending). You could also use a simple kyverno policy to replace the images at runtime, which could be easier to maintain.
628
648
- **Q:** Why does Kubeflow use Istio CNI instead of standard Istio?
629
649
**A:** Istio CNI provides better security by eliminating the need for privileged init containers, making it more compatible with Pod Security Standards (PSS). It also enables native sidecars support introduced in Kubernetes 1.28, which helps address issues with init containers and application lifecycle management.
630
650
- **Q:** Why does Istio CNI fail on Google Kubernetes Engine (GKE) with "read-only file system" errors?
0 commit comments