-
Notifications
You must be signed in to change notification settings - Fork 22
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
submariner: support #20
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mockup
Just a mockup with a static JSON file to show how we would want to depict submariner:
You can find the mockup code here: https://github.com/hunchback/skydive-ui/tree/submariner-mockup
Development Setup
You can install submariner (using e2e test setup) and then install Skydive in a multi-cluster setup:
skydive analyzer cluster1
skydive analyzer cluster2
skydive analyzer broker
Topology
We basically want to be able to identify:
And then depict the links between these nodes.
Use current k8s probe
So you enable the probe in cluster1 and cluster2
You use k8s metadata Labels fields to identify various submariner elements
Extend k8s probe to also capture CRDs
This means we have to support understanding CRD templates and CRD objects (which represent submariner control plane).
Add a dedicated submariner probe
The broker has an API which can be queried and used to understand the submariner topology.
Flows
By understand submariner topology we can now track flows crossing between clusters (via the IPSec tunnel) and ensure they are associated and thus can be tracked across boundaries
The text was updated successfully, but these errors were encountered: