CSS-3448: Add UI relation #13
Merged
Conversation
This file contains 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
kelkawi-a
requested review from
frankban,
kian99,
TeodorPt,
maabujayyab,
mertalpt,
gtato and
AmberCharitos
kian99
approved these changes
Mar 27, 2023
TeodorPt
approved these changes
Mar 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note
With the introduction of the UI charm integration, we will now have two types of traffic to support through the ingress: gRPC (for the server) and HTTP (for the UI). As we have not yet implemented TLS functionality on this charm, both of these traffics will be funneled through port 80, which cannot multiplex between them. Therefore, as a temporary workaround, we will access gRPC traffic on port 80 as done previously, and access HTTP traffic (the web UI) on port 443.