Add POD_NAME env to vl3-nse to be able to resolve the NSE name by DNS #8558
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
Signed-off-by: Artem Glazychev <artem.glazychev@xored.com>
denis-tingaikin
approved these changes
Feb 6, 2023
nsmbot
pushed a commit
to networkservicemesh/integration-tests
that referenced
this pull request
Feb 6, 2023
…ployments-k8s@main PR link: networkservicemesh/deployments-k8s#8558 Commit: 9c74814 Author: Network Service Mesh Bot Date: 2023-02-01 04:44:45 -0600 Message: - Update go.mod and go.sum to latest version from networkservicemesh/de… Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
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.
Signed-off-by: Artem Glazychev artem.glazychev@xored.com
Description
If we add
POD_NAMEenv to vl3-NSE we will be able to resolve endpoint DNS nameIssue link
networkservicemesh/sdk#1414
How Has This Been Tested?
Types of changes