[Nova] Use internal endpoint to talk to Cinder #9983
Draft
Conversation
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
Talking to Cinder via Nginx-Ingress instead of cluster-internal adds additional points that can fail in the communication. It also prevents us to use the new cinder-api-internal Deployment we're going to introduce. We run the risk of getting additional 500 errors produced by linkerd-proxy connection problems, since the internal endpoints use HTTP instead of HTTPS.
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.
Talking to Cinder via Nginx-Ingress instead of cluster-internal adds additional points that can fail in the communication. It also prevents us to use the new cinder-api-internal Deployment we're going to introduce.
We run the risk of getting additional 500 errors produced by linkerd-proxy connection problems, since the internal endpoints use HTTP instead of HTTPS.