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.

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

ArgoCD Vault Plugin Spike (aka Secrets Spike) #2914

Closed
nelsestu opened this issue Apr 30, 2024 · 2 comments
Closed

ArgoCD Vault Plugin Spike (aka Secrets Spike) #2914

nelsestu opened this issue Apr 30, 2024 · 2 comments
Assignees

Comments

@nelsestu
Copy link
Contributor

nelsestu commented Apr 30, 2024

User Story

As a VRO Engineer, I want to identify the scope of any secret refactoring work that is necessary in order to make an informed decision about ArgoCD.

Acceptance Criteria

  1. Identify the optimal solution for VRO's mixed content type secrets
    a. Can VRO's use of mixed content type secrets work in ArgoCD vault plugin?
  2. Identify whether ArgoCD Vault Plugin allows for any configuration overhead reduction
    a. what is the potential implementation for mapping a directory of secrets
    b. if one to one mapping is required, then how many individual secrets are we talking about?
  3. Achieve a fully functioning BIP service. The POC successfully deployed the BIP service, however, startup of the service was failing on secret inflation.

Notes about work

@nelsestu nelsestu self-assigned this Apr 30, 2024
@nelsestu nelsestu changed the title ArgoCD Vault Plugin Spike ArgoCD Vault Plugin Spike (aka Secrets Spike) May 1, 2024
@nelsestu
Copy link
Contributor Author

nelsestu commented May 6, 2024

Having presented the team with the ArgoCD POC, there was mixed response, and while the spec review seemed to indicate a "yes" we should use ArgoCD, the POC left the team with less confidence. Following the demo, the team continued sharing feedback and concerns in slack. While inconclusive, Megan and Erik met the following monday, and resolved to try and mitigate/eliminate some of the team's concerns with a spike that would dive into secrets more deeply. As my health declined throughout the rest of last week, it complicated working on this issue. At no point was this issue going particularly well, and while I was able to continue experimenting with the secrets retrieval mechanisms in ArgoCD, I was still struggling to resolve the mysterious "default branch" issue, which had broken part of the POC. So finally after significant pain and multiple things still pointing towards giving up on ArgoCD, I spent some of Monday morning continuing with experiments I began over the weekend... and just prior to sprint retro, I finally declared defeat.

@BerniXiongA6
Copy link

Closing ticket since Erik's work is done. Berni will create a workshop to regroup as a team to discuss alternatives (meeting invite for team to come).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants