option to use HTTPS protocol when TLS is provided externally - #166
Merged
Tim-herbie merged 3 commits intoSep 6, 2026
Merged
Conversation
Owner
|
Hey @zone-zero thank you for your pr. |
Owner
|
I merged the pr. You can use this tag for the helm-chart: 3.0.1-pre-release-c537d54 I will probably release the change with the next OpenCloud update. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With the 3.0.0 update, opencloud was set to use HTTP URLS for the web interface when internal TLS was disabled and/or the internal IDP was disabled. This isn't always desirable if TLS is provided externally.
this caused CORS and script source issues when using an external proxy to provide TLS services to a users.
I added the .Values.opencloud.tls.external value (true by default) to instruct opencloud to use HTTPS urls even if it wasn't configured internally.