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

[bitnami/apisix] Unable to disable tls on control-plane #24594

Closed
jorgenll opened this issue Mar 21, 2024 · 3 comments · Fixed by #24600
Closed

[bitnami/apisix] Unable to disable tls on control-plane #24594

jorgenll opened this issue Mar 21, 2024 · 3 comments · Fixed by #24600
Assignees
Labels
apisix solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@jorgenll
Copy link
Contributor

Name and Version

bitnami/apisix 3.0.0

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Set the parameter controlPlane.tls.enabled=false
  2. Generate the template

Are you using any custom parameters or values?

-- set controlPlane.tls.enabled=false

What is the expected behavior?

If we disable the tls on the controlPlane, the Secret apisix-control-plane-tls isn't generated

What do you see instead?

The Secret apisix-control-plane-tls is generated. If additionally the parameters controlPlane.tls.autoGenerated is set to false, the secret is generated without data

Additional information

Reviewing the template tls-secret.yaml file, exists a difference between the configuration for the data-plane and the control-plane.
The following if sentence miss the check .Values.controlPlane.tls.enabled.
The current if:

{{- if and .Values.controlPlane.enabled (not .Values.controlPlane.tls.existingSecret) }}

The expected if:

{{- if and .Values.controlPlane.enabled .Values.controlPlane.tls.enabled (not .Values.controlPlane.tls.existingSecret) }}
@jorgenll jorgenll added the tech-issues The user has a technical issue about an application label Mar 21, 2024
@github-actions github-actions bot added the triage Triage is needed label Mar 21, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

@jorgenll
Copy link
Contributor Author

Great, I'll create the pull request with the fix.
Additionally, I've see a similar issue trying to disable the tls on the ingress-controller. I'll include both fixes on the PR

@carrodher
Copy link
Member

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apisix solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants