Releases

Kubeflow v1.11.0 is a major feature release with significant infrastructure and security shifts: the default S3 backend moves from MinIO to Seaweedfs, Istio sidecar scope is pruned by default, and PodSecurityStandards enforcement is tightened for both system and user namespaces. Operators need to back up MinIO data, verify PSS compliance, and confirm they're on Kubernetes 1.33+ with Kustomize 5.7.1 before upgrading.

• breakingBack up MinIO data before upgrading

  MinIO is replaced by Seaweedfs as the default S3 storage backend. This is a transparent switch, but any data currently on MinIO needs to be backed up and restored manually before or during the upgrade.

• breakingCheck PodSecurityStandards compliance in system and user namespaces

  System namespaces now enforce the restricted PodSecurityStandards level, and user namespaces enforce baseline. Workloads or pods that previously relied on more permissive security contexts may be blocked; audit manifests in system and user namespaces for PSS compliance before rolling out.

• breakingReview Istio sidecar scope after mesh pruning

  Istio sidecar scope is now pruned/limited by default instead of covering the full mesh, cutting sidecar memory and network overhead on large clusters. Cross-namespace or cross-service traffic that depended on full mesh visibility should be validated after upgrade.

• breakingZero pod overhead is now the default for namespaces/profiles

  Namespaces and profiles now default to zero pod overhead, roughly halving the number of overhead pods per namespace. Confirm no workloads relied on the previous per-namespace overhead pods before upgrading.

• breakingConfirm Kubernetes 1.33+ and Kustomize 5.7.1 before upgrading

  Kubeflow v1.11.0 supports Kubernetes 1.33+ and is tested against Kustomize 5.7.1. Running older Kubernetes or a different Kustomize version is degraded/unsupported and may cause manifest or deployment issues.

• breakingPlan migration off deprecated Bitnami components

  Bitnami-based components are now deprecated in this release. Plan migration away from Bitnami images/charts where used, as they may be replaced or removed in a future release.