Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rework Deletion Mechanism #15

Open
thatInfrastructureGuy opened this issue Jan 18, 2020 · 0 comments
Open

Rework Deletion Mechanism #15

thatInfrastructureGuy opened this issue Jan 18, 2020 · 0 comments
Assignees
@thatInfrastructureGuy
Labels
help wanted Extra attention is needed

Comments

@thatInfrastructureGuy
Copy link
Owner

thatInfrastructureGuy commented Jan 18, 2020 •
edited
Loading

With current architecture we cannot delete the keys from providers (azure, aws) etc. We currently rely on date timestamps to update the keys. Deletion of key gets rid of metadata.

Workarounds:

  1. [Providers: All] Delete the kubernetes secret and resync.
  2. [Providers: AWS] Set the key value to "". Resync. Delete the key from secretsmanager.
  3. [Providers: Azure] Disable / Expire / Deactivate the secret in keyvault.
@thatInfrastructureGuy thatInfrastructureGuy added the enhancement New feature or request label Jan 18, 2020
@thatInfrastructureGuy thatInfrastructureGuy self-assigned this Jan 18, 2020
@thatInfrastructureGuy thatInfrastructureGuy added wontfix This will not be worked on bug Something isn't working help wanted Extra attention is needed and removed enhancement New feature or request wontfix This will not be worked on bug Something isn't working labels Jan 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thatInfrastructureGuy thatInfrastructureGuy

Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thatInfrastructureGuy