velero-io/velero

Support additional labels and annotations on velero CLI generated YAML

Open

#4.982 geöffnet am 10. Juni 2022

Auf GitHub ansehen
 (2 Kommentare) (6 Reaktionen) (0 zugewiesene Personen)Go (1.550 Forks)auto 404
Help wantedkind/requirement

Repository-Metriken

Stars
 (10.111 Stars)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

Describe the problem/challenge you have We installed velero with velero install command and it worked well. But we recently added a kyverno policy that checked if a specific label is existing on all namespaces, and this causes a policy violation each time the velero pipeline is launched because the label is missing on velero namespace. The namespace is generated by the CLI each time the velero install command is launched and it seems not possible to add labels or annotations to resources generated by the CLI.

Describe the solution you'd like The velero install command could support additional labels and annotations to be compliant to policy engines rules.

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • :+1: for "The project would be better with this feature added"
  • :-1: for "This feature will not enhance the project in a meaningful way"

Contributor Guide