Skip to content

Rule-based secret selector #2

Closed

Description

@nightkr

Rather than naming the secret explicitly (#1), a Volume should be matchable to a Secret based on dynamic criteria (such as the pod name, controller object, service name, node name, and so on).

Activity

  1. added a commit that references this issue on Nov 30, 2021
    48f6da9
  2. self-assigned this
    on Dec 1, 2021
  3. added a commit that references this issue on Dec 17, 2021
    3fc888c
  4. added a commit that references this issue on Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions