-
Notifications
You must be signed in to change notification settings - Fork 17
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
FRR-K8s: make listening to incoming connections configurable #229
Conversation
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.
General questions:
When metallb deploys the frr-k8s backend, it used HELM right? So the default will be no incoming connections? When we use operator the operator deploys the metallb and that deploys the backend, right?
charts/frr-k8s/values.yaml
Outdated
@@ -163,6 +163,8 @@ frrk8s: | |||
metricsPort: 7573 | |||
resources: {} | |||
secureMetricsPort: 9141 | |||
# frr contains configuration specific to the FRR container, |
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 do not understand the comment, can you expand?
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.
because it's a copy / paste mistake :D
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.
removed
re: metallb: it depends. If it uses kustomize, it will need to provide a custom configmap / kustomize override it. With helm, it uses helm. The operator uses helm |
In case full mesh is not needed, always connecting results in a more predictable behavior. Signed-off-by: Federico Paolinelli <[email protected]>
c2bb74b
to
46dcc92
Compare
CI failed in GR test and logs
and
It looks again that route-map was
and the BGPD crashed (because pid was not found). |
Is this a BUG FIX or a FEATURE ?:
What this PR does / why we need it:
In case full mesh is not needed, always connecting results in a more predictable behavior. So let's let the user choose if they want to accept connectoins or not.
Special notes for your reviewer:
Release note: