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

feat: set probe scheme to HTTPS when TLS is enabled #144

Merged
merged 6 commits into from
Nov 15, 2023
Merged

feat: set probe scheme to HTTPS when TLS is enabled #144

merged 6 commits into from
Nov 15, 2023

Conversation

PurseChicken
Copy link
Contributor

@PurseChicken PurseChicken commented Nov 14, 2023

This fixes #143

Definition of Ready

  • I am happy with the code
  • Short description of the feature/issue is added in the pr description
  • PR is linked to the corresponding user story
  • Acceptance criteria are met
  • All open todos and follow ups are defined in a new ticket and justified
  • Deviations from the acceptance criteria and design are agreed with the PO and documented.
  • No debug or dead code
  • My code has no repetitions
  • Documentation/examples are up-to-date
  • All non-functional requirements are met
  • If possible, the test configuration is adjusted so acceptance tests cover my changes

This PR sets the liveliness, readiness and startup probe schemes to HTTPS if TLS is enabled in configmapConfig.
Without setting scheme: HTTPS it defaults to HTTP which causes the probes to fail and the pod(s) never report as healthy.

@PurseChicken PurseChicken marked this pull request as ready for review November 14, 2023 22:18
Copy link
Member

@eliobischof eliobischof left a comment

Choose a reason for hiding this comment

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

Thanks for the PR 🙏

Can you please increment the chart version in the Chart.yaml?

Also, if we enable the probes in the self-signed example, the tests should pass, right?

charts/zitadel/templates/deployment.yaml Outdated Show resolved Hide resolved
@PurseChicken
Copy link
Contributor Author

Thanks for the PR 🙏

Can you please increment the chart version in the Chart.yaml?

Also, if we enable the probes in the self-signed example, the tests should pass, right?

Do want a patch bump to 7.2.1?

And yes, if we implement this, and enable the probes in the self-signed example, the probes will succeed.

charts/zitadel/Chart.yaml Outdated Show resolved Hide resolved
Copy link
Member

@eliobischof eliobischof left a comment

Choose a reason for hiding this comment

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

Nice, this seems to work 👍
Thank you @PurseChicken 🎉

@eliobischof eliobischof changed the title fix: Set Probe scheme to HTTPS when TLS is enabled feat: set Probe scheme to HTTPS when TLS is enabled Nov 15, 2023
@eliobischof eliobischof changed the title feat: set Probe scheme to HTTPS when TLS is enabled feat: set probe scheme to HTTPS when TLS is enabled Nov 15, 2023
@eliobischof eliobischof enabled auto-merge (squash) November 15, 2023 02:40
@eliobischof eliobischof merged commit 8981cd8 into zitadel:main Nov 15, 2023
8 checks passed
kleberbaum pushed a commit to fhkit/zitadel-charts that referenced this pull request May 24, 2024
* Change scheme to HTTPS on probes when TLS is enabled.

* Fix issue with potential NIL pointer if TLS is undefined.

* bump minor version of chart and update to latest appVersion

* Remove disabling probes from self-signed example

* Use deepCheck helper for TLS.Enabled

* Add newline to chart.yaml so linting succeeds
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.

Deployment probes fail when using TLS Enabled
2 participants