Skip to content

Conversation

@elamaran11
Copy link
Contributor

Bug Fix to add Ingress for ArgoCD

@elamaran11 elamaran11 force-pushed the fix/missingArgoCDIngress branch from eb7a114 to 5757748 Compare August 29, 2024 21:40
Signed-off-by: Elamaran Shanmugam <[email protected]>
Signed-off-by: Elamaran Shanmugam <[email protected]>
Signed-off-by: Elamaran Shanmugam <[email protected]>
@elamaran11 elamaran11 force-pushed the fix/missingArgoCDIngress branch from e2699d7 to dfbe046 Compare August 29, 2024 21:54
@nimakaviani nimakaviani self-requested a review August 29, 2024 22:10
Copy link
Contributor

@nimakaviani nimakaviani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, as long as the risks of exposing Argo CD to the internet are assessed.

ideally, this should be done in an ephemeral cluster for testing purposes only. As @nabuskey said, Compromised ArgoCD = compromised cluster = compromised AWS account.

@nimakaviani nimakaviani merged commit c5f0748 into cnoe-io:main Aug 29, 2024
@elamaran11 elamaran11 deleted the fix/missingArgoCDIngress branch August 30, 2024 00:11
@elamaran11
Copy link
Contributor Author

Agreed @nimakaviani . This is more of ingress for ArgoCD following the same principles with ingress for others. We should be good.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants