WIP: Implements automatically setting up nexd proxy ingress/egress rules using skupper config.#1221
WIP: Implements automatically setting up nexd proxy ingress/egress rules using skupper config.#1221chirino wants to merge 7 commits intonexodus-io:mainfrom
Conversation
✅ Deploy Preview for nexodus-docs canceled.
|
|
@chirino, this pull request is now in conflict and requires a rebase. |
Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
… using a skupper config file. Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
… discover service locations. Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
…gress proxies get removed. Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
…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 <hiram@hiramchirino.com>
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.
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.shto 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.shto 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.shto see the ingress/egress rules that get created on each nexd running in proxy mode.