-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vL3 load balancer example #9830
vL3 load balancer example #9830
Conversation
Signed-off-by: Artem Glazychev <[email protected]>
2cd2901
to
e3101ba
Compare
- name: POD_NAME | ||
value: "finance" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need a hardcoded pod name env here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use POD_NAME as DNS name in vl3 examples
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's worth mentioning in the readme file or adding a comment in the yaml file.
So that if someone wants to replicate vl3-lb setup it's clear what they should change.
I think, ideally there should be a different solution.
Each pod gets <pod-name>.vl3-domain
address, and additionally some pods may get more DNS addresses.
Signed-off-by: Artem Glazychev <[email protected]>
e3101ba
to
40af724
Compare
…ployments-k8s@main PR link: networkservicemesh/deployments-k8s#9830 Commit: 876dd11 Author: Network Service Mesh Bot Date: 2023-09-25 23:30:08 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/de… Signed-off-by: NSMBot <[email protected]>
Description
Issue link
#9210
How Has This Been Tested?
Types of changes