Skip to content

Application v3 manifest - Istio and Dex #1424

@PatrickXYS

Description

@PatrickXYS

Ref: #1062

I wonder if we'll migrate Istio and Dex components to V3. It will be great for us to have at least a base_v3 directory under the components folder.

By following below principals to establish base_v3 without changing original base+overlay folder:

Applications in KFDef should not use parameters field
Applications should fetch global paramaters from the configmap "kubeflow-config"
Applications should fetch application parameters from application specific config maps
Application specific config maps should be named "${APPNAME}-config"
Use of vars should be minimized
The most common and supported use case should be to substitute parameters into
fields that don't support referencing a configmap directly
In this case var names should be unique enough that they won't conflict with vars from
other applications

Since we AWS side has dependencies on Istio and Dex, there's motivation for us to help with migration.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions