How kubeflow/manifests works
Project’s Purpose and Type
• It is not a traditional “application codebase” but an extensive set of configuration manifests for a full-scale ML platform deployment.
• The repository’s aim is to install the entire Kubeflow ecosystem (components such as Pipelines, KServe, Notebook Controllers, Central Dashboard, Training Operator, etc.) onto a Kubernetes cluster.
• It uses Kustomize overlays to support multiple environments and integrate with common supporting services (Istio, Dex, cert-manager, oauth2-proxy, knative, etc.).
File Structure
• The top-level directories break into key areas:
– “apps”: Contains Kubeflow’s official components (each subfolder represents a separate Kubeflow component/application).
– “common”: Holds shared infrastructure components such as cert-manager, dex (for authentication), istio (for service mesh and ingress), knative, network policies, oauth2-proxy, and others.
– “experimental”: Features third-party integrations (like Ray, SeaweedFS) and experimental deployments.
– Other directories such as “proposals”, “scripts”, and “tests” provide adjunct support.
• This organization highlights an architecture based on multiple independent pieces that are typically deployed into different Kubernetes namespaces; some components (like Istio or Dex) support external authentication and routing across several Kubeflow applications.
README for Architectural Insights
• The README explains that users can deploy either the entire platform or individual components, making the system design modular.
• It describes how individual components are maintained separately and then “stitched together” through centralized authentication (using Dex coupled with oauth2-proxy) and networking (using Istio as the ingress gateway).
• The dependency matrix provided (with upstream revisions for each component) emphasizes that every major Kubeflow service (e.g., pipelines, notebook controller, katib, central dashboard) is integrated under a common infrastructure environment.
Main Components and Their Relationships
◦ Ingress & Networking: Represent Istio (ingress gateways, virtual services, destination rules) and external connectivity (port-forward, NodePort/LoadBalancer concepts).
◦ Authentication & Identity: Capture Dex (as an OpenID Connect identity provider), oauth2-proxy (to extend Istio’s ingress functionality), and the associated configuration overlays.
◦ Core Kubeflow Applications: These include Pipelines, Notebook Controller, Central Dashboard, Tensorboards Web App, Profiles controller, Training Operator, PVC Viewer, Volumes Web App, and KServe along with its Models Web App.
◦ Shared/common Services: Include cert-manager (for managing TLS certificates), network policies, common roles (kubeflow-view/edit/admin) and namespaces.
◦ Experimental/Third-Party Modules: We can annotate that there are experimental modules (like Ray and SeaweedFS) for advanced experimentation.
• Directional flows:
◦ Traffic enters via the Istio Ingress Gateway.
◦ Authentication flows: The Ingress routes through oauth2-proxy which uses Dex to validate credentials.
◦ Once authenticated, user sessions and API calls are routed to various Kubeflow components (e.g., Pipeline API, Notebook server, Dashboard).
◦ Internal communication is secured by Istio routing rules and mutual TLS established with cert-manager support.
Important Architectural Patterns and Connections
• Modular and overlay-based design approach using Kustomize. This is visible in the file tree (several “overlays” directories per service).
• How external dependencies (authentication, identity, network security) are decoupled from individual business components.
• That each component is independently deployable yet integrates with shared common services.