nvmeof: resolve listener hostname into IP-address #5996
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
This allows a configuration in the StorageClass with listeners set to a Kubernetes Service hostname and IP-address 0.0.0.0. This means the gateway listens on the wildard IP-address, and the node-plugin can use the IP-address of the Kubernetes Service to connect to. Signed-off-by: Niels de Vos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This allows a configuration in the StorageClass with listeners set to a Kubernetes Service hostname and IP-address 0.0.0.0. This means the gateway listens on the wildard IP-address, and the node-plugin can use the IP-address of the Kubernetes Service to connect to.
Note: This PR is for testing only.
quay.io/nixpanic/cephcsi:nvmeofis a container buildt from this PR./cc @OdedViner @gadididi
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)