-
Notifications
You must be signed in to change notification settings - Fork 26
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
WIP: Implements automatically setting up nexd proxy ingress/egress rules using skupper config. #1221
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for nexodus-docs canceled.
|
@chirino, this pull request is now in conflict and requires a rebase. |
Signed-off-by: Hiram Chirino <[email protected]>
Signed-off-by: Hiram Chirino <[email protected]>
… using a skupper config file. Signed-off-by: Hiram Chirino <[email protected]>
… discover service locations. Signed-off-by: Hiram Chirino <[email protected]>
…gress proxies get removed. Signed-off-by: Hiram Chirino <[email protected]>
…rgeted by services created by the skupper service controller. Also improved the PoC scripts so that your can fully replace the skupper router plane with the nexodus router. Signed-off-by: Hiram Chirino <[email protected]>
hack/skupper/install-skupper.sh
Outdated
|
||
# | ||
# Deploy nexodus proxy routers that will proxy services based on the skupper config: | ||
kubectl config set-context --current --namespace west |
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.
One thing that bit me was that if you run two separate scripts at the same time that are nothing using kubectl config set-context
, they'll break each other. I did that with some performance testing I was doing.
@chirino very cool PoC -- is it posted here for easy discussion and testing? or were you proposing that it be merged? Maybe we should create a new repo for skipper integration. We could run the config controller as a sidecar container in the nexd container that uses either nexctl or the socket interface directly for managing rules. |
Yeah. Right now it's here for easy sharing. We can move this around to a different process if we figure out the final desires architecture. |
@chirino, this pull request is now in conflict and requires a rebase. |
@chirino, this pull request is now in conflict and requires a rebase. |
To test out the PoC:
make run-on-kind
../hack/skupper/install-skupper.sh
to install skupper. This will bring up a browser to an app which uses skupper's dataplane to connect the frontend app to the backend service../hack/skupper/replace-with-nexodus.sh
to replace the skupper router with a nexodus implementation. This will bring up a browser to an app which uses nexodus dataplane to connect the frontend app to the backend service../hack/skupper/proxy-status.sh
to see the ingress/egress rules that get created on each nexd running in proxy mode.