-
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
chore(bgp): documentation on new bgp nat gw feature #186
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.
Thanks for the docs.
I tried it it seems we have to change default subnet's provider to the nad you created here. I tried without it failed, changed it it can talk to api-server.
Update:
NVM, it still fails i will try to debug it.
It works bug i don't know how and why? Sometimes it can connect to the api-server and sometimes it can not, and i try this by deleting nat-gw and creating it again, maybe there is something wrong with my setup idk. |
You're right about changing the provider of the default subnet, I edited the docs to reflect that. |
@SkalaNetworks
And when it's ok it will show something like this:
Both reports generated by just deleting and recreating the same schema. |
Also can we log if the connection to the neighbor is not available? |
Can you print the YAML of the NAT GW pod when it fails to connect to the API? |
For sure next that happens i will forward it to you. Maybe my setup is buggy i changed it a lot. |
No description provided.