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

[BUG] TLS secret naming is incorrect when deployed using Helm #655

Open
PhanLe1010 opened this issue Aug 3, 2023 · 0 comments
Open

[BUG] TLS secret naming is incorrect when deployed using Helm #655

PhanLe1010 opened this issue Aug 3, 2023 · 0 comments
Labels
area/kubernetes k8s and related kind/bug Something isn't working triage/proposal for closure There are reasons for this issue to be closed

Comments

@PhanLe1010
Copy link

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Deploy s3gw chart v0.18.0 using Rancher UI
  2. Somehow the TLS secret has some random suffix that confused the Traefix ingress

Screenshot from 2023-08-03 08-40-30

Traefik failed with the error:

time="2023-08-03T05:30:35Z" level=error msg="Error configuring TLS: secret s3gw/s3gw-ui-ingress-tls does not exist" ingress=longhorn-s3-ui namespace=s3gw providerName=kubernetes
time="2023-08-03T05:30:35Z" level=error msg="Error configuring TLS: secret s3gw/s3gw-ingress-tls does not exist" namespace=s3gw providerName=kubernetes ingress=longhorn-s3

Expected behavior A clear and concise description of what you expected to
happen.

TLS secrete name shouldn't have the random sufix
@github-actions github-actions bot added the triage/waiting Waiting for triage label Aug 3, 2023
@jhmarina jhmarina added this to the v.0.20.0 milestone Aug 7, 2023
@m-ildefons m-ildefons added kind/bug Something isn't working area/kubernetes k8s and related and removed triage/waiting Waiting for triage labels Aug 7, 2023
m-ildefons referenced this issue in m-ildefons/s3gw-charts Aug 8, 2023
@m-ildefons
Fix and test self-signed issuer
e1d497b 
- Fix the name of the self-signed issuer in the annotation of the
  ingress.
- Add test ensuring the certificates and ingresses and annotations are
  created as expeced
- Fix broken tests for COSI RBAC resources

Fixes: aquarist-labs/s3gw#655
Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
@m-ildefons m-ildefons mentioned this issue Aug 8, 2023
Closed
3 tasks
This was referenced Aug 14, 2023
Open
Open
@jhmarina jhmarina modified the milestones: v.0.20.0, v.0.21.0 Sep 4, 2023
@jecluis jecluis added the triage/proposal for closure There are reasons for this issue to be closed label Mar 21, 2024
@jecluis jecluis removed this from the v0.24.0 milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/kubernetes k8s and related kind/bug Something isn't working triage/proposal for closure There are reasons for this issue to be closed
Projects
s3gw
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jecluis @jhmarina @m-ildefons @PhanLe1010