Skip to content

Smarter k8s/config plugins decisions #3

@lberk

Description

@lberk

Similar to issue #2 where we need to fix the resource release versions being hardcoded, we should have a smarter approach to our underlying k8s version, and the extra configuration options we need to pass to the api server.
Could probably also be done with an associative array?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions