Skip to content

Pass task required properties from overlord to task pod #17773

@FrankChen021

Description

@FrankChen021

Description

Image

As stated by the doc above, these two properties should be configured to peon tasks.

However, these two properties should be only present at the overlord side to create a task POD, and if task pod really needs these two properties, overlord should pass these two to task POD in the background for users.

Managing thes properties in K8S is tedious, because we have to keep two copies of these properties, one at the overlord side, another at the peon side.

Removing these two from peon would help ease the configuration.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions