Skip to content

Need a concise way to trigger a refresh for a ClusterExternalSecret #987

@sarasensible

Description

@sarasensible

Describe the solution you'd like
Trigger a refresh of all external secrets managed by a ClusterExternalSecret

What is the added value?
Secret refreshing will make internal secrets up to date with cluster external secrets

Give us examples of the outcome

kubectl annotate ces my-es force-sync=$(date +%s) --overwrite would trigger a refresh of all secrets managed by that ces.

Observations (Constraints, Context, etc):

This can be worked around by iterating over the namespaces that the ClusterExternalSecret manages but it is awkward, for example:

NAMESPACES=$(kubectl get ns -l global-secrets=true | tail -n+2 | awk '{print $1}'); for NAMESPACE in $NAMESPACES; do kubectl annotate es my-secret -n $NAMESPACE  force-sync=$(date +%s) --overwrite ; done

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    StaleThis issue/Pull Request is stale and will be automatically closedarea/lifecycleIndicates an issue related to the lifecycle of secretsgood first issueGood for newcomerskind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions