hashicorp / hashicorp/vault-secrets-operator

managing rolloutRestartTargets with dynamic/changing names

Open
#965 0 comments 6 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
600
Forks
146
Avg merge
3d 8h
Merged PRs (30d)
6

Description

**Is your feature request related to a problem? Please describe.**
each time we update a deployment or configmap its name is being updated, we add the update number to its name, for example:
```
rolloutRestartTargets:
- kind: Deployment
name: mydeploy-00014-deployment
```
this is making it impossible to add these deployments to the "rolloutRestartTargets"

**Describe the solution you'd like**
i would like to:
* have the option to add a wildcard to the name like: mydeploy-*-deployment
* have an alternate way to mark specific deployments/configmaps/etc for rollout somehow, mybe via tags or labels.

**Describe alternatives you've considered**
I understand that reloader can automatically trigger restarts/rollouts by watching labels.

**Additional context**
i would like to keep using the official Hashicorp operator, and cannot change my convention of deployment names.

thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the rolloutRestartTargets configuration and the existing label-based restart behavior described in the issue. Compare wildcard matching with label or tag selection for dynamically named Deployments, ConfigMaps, and related resources. Done means one supported way can target changing names without requiring updates to the configuration, with behavior documented and covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.