Skip to content

Reference secret in manifestwork instead of putting raw data in it. #46

Closed as not planned

Description

@qiujian16

Activity

  1. qiujian16 commented on Mar 28, 2022

    @qiujian16
    MemberAuthor

    /assign @qiujian16

  2. bhperry commented on Feb 12, 2025

    @bhperry
    Contributor

    This would be great. The Policy add-on I think partially solves this problem by supporting encrypted values, and I'm guessing if you bind your ManifestWorkReplicaSet and secret Policy to the same Placement then you would get the desired behavior of secret(s) being created for each ManifestWork that is distributed out to spoke clusters.

    It would be nice to have support for this in OCM core though

  3. ocm-bot commented on Jul 20, 2026

    @ocm-bot

    This issue/PR is marked stale and will be closed in 30 days unless there is new activity.

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