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

fix(argo-cd): Enable Redis authentication in the default installation #2705

Merged
merged 2 commits into from
May 21, 2024

Conversation

mkilchhofer
Copy link
Member

@mkilchhofer mkilchhofer commented May 21, 2024

See GHSA as soon as it's published:
GHSA-9766-5277-j5hr

* fix: Implement redis authentication

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

chore: Rework as a Kubernetes Job (use ingress-nginx/cert-manager approach)

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

fix: Implement redis probes (add auth)

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

feat: Add some standardization on the newly added resources

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

fix: Ensure externalRedis is still working properly

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

fix: Use correct ServiceAccount in Job

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

* docs: Add note about secret rotation, bump chart version

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

* chore: Use final appVersion from upstream

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>

---------

Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>
Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>
@mbevc1
Copy link
Collaborator

mbevc1 commented May 21, 2024

@mkilchhofer seems your signing GPG expired?

@mkilchhofer
Copy link
Member Author

mkilchhofer commented May 21, 2024

@mkilchhofer seems your signing GPG expired?

Should not block the PR here :D Issue is my new mail addy due to my new last name
image

@mkilchhofer mkilchhofer merged commit fcee9a6 into main May 21, 2024
6 checks passed
@mkilchhofer mkilchhofer deleted the bugfix/argo-cd_redis_auth branch May 21, 2024 16:36
@nbarrientos
Copy link
Contributor

Hi,

May I ask if this will be backported to 6.7.x (chart supporting Argo CD 2.10.x)?

@yu-croco
Copy link
Collaborator

Hi @nbarrientos ,
To be honest we don't support backport patch... I wonder you can update Helm Chart with fixing Argo CD tag to v2.10.x via values.yaml.
Ref:

@nbarrientos
Copy link
Contributor

Thanks. Do versions of the Helm chart newer than 6.7.x (e.x. 6.10.0) support Argo CD v2.10.x? For instance since this commit they might not but it's not clear to me what's the lower bound of supported Argo CD versions when you bump Chart.yaml.appVersion. In short, how can I tell what's the minimum Argo CD supported by a given version of the chart? Thanks again!

@mkilchhofer
Copy link
Member Author

@yu-croco
This does not work since the 2.10 chart does not contain the newly added Job

@yu-croco
Copy link
Collaborator

Oh I see... 😭

@nbarrientos
Copy link
Contributor

Thanks. Do versions of the Helm chart newer than 6.7.x (e.x. 6.10.0) support Argo CD v2.10.x? For instance since this commit they might not but it's not clear to me what's the lower bound of supported Argo CD versions when you bump Chart.yaml.appVersion. In short, how can I tell what's the minimum Argo CD supported by a given version of the chart? Thanks again!

Shall I open an issue to discuss this further?

@mkilchhofer
Copy link
Member Author

Shall I open an issue to discuss this further?

Yes that would be more intuitive than discussing on a closed PR.

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

Successfully merging this pull request may close these issues.

None yet

6 participants