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

docs: nginx passthrough secret as argocd-server-tls #12921

Conversation

jdg-journeyfront
Copy link
Contributor

@jdg-journeyfront jdg-journeyfront commented Mar 17, 2023

As documented in tls.md § "TLS certificates used by argocd-server", the secret that should be modified by cert-manager is not argocd-server but argocd-server-tls should be created instead.

The ingress-nginx controller doesn't like using a secret of type: Opaque.

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

@jdg-journeyfront jdg-journeyfront changed the title Doc nginx passthrough secret as argocd-server-tls docs nginx passthrough secret as argocd-server-tls Mar 17, 2023
As documented in tls.md § "TLS certificates used by argocd-server", the secret that should be modified by cert-manager is not `argocd-server` but `argocd-server-tls` should be created instead.

The ingress-nginx controller doesn't like using a secret of `type: Opaque`.

Signed-off-by: Josh Gardner <111776680+jdg-journeyfront@users.noreply.github.com>
@jdg-journeyfront jdg-journeyfront force-pushed the update-doc-nginx-passthrough-secret branch from ad6275e to 7a738e1 Compare March 27, 2023 22:26
@codecov
Copy link

codecov bot commented Mar 27, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (82f006c) 48.94% compared to head (7a738e1) 48.94%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #12921   +/-   ##
=======================================
  Coverage   48.94%   48.94%           
=======================================
  Files         246      246           
  Lines       42435    42435           
=======================================
  Hits        20770    20770           
  Misses      19555    19555           
  Partials     2110     2110           

see 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@crenshaw-dev crenshaw-dev changed the title docs nginx passthrough secret as argocd-server-tls docs: nginx passthrough secret as argocd-server-tls Apr 4, 2023
Copy link
Member

@34fathombelow 34fathombelow left a comment

Choose a reason for hiding this comment

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

Lgtm!

Copy link
Member

@jannfis jannfis left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@jannfis jannfis merged commit 4b7f7c3 into argoproj:master May 3, 2023
yyzxw pushed a commit to yyzxw/argo-cd that referenced this pull request Aug 9, 2023
As documented in tls.md § "TLS certificates used by argocd-server", the secret that should be modified by cert-manager is not `argocd-server` but `argocd-server-tls` should be created instead.

The ingress-nginx controller doesn't like using a secret of `type: Opaque`.

Signed-off-by: Josh Gardner <111776680+jdg-journeyfront@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants