skydive-project/skydive-operator

skydive-operator's Issues

Browser hangs and takes too long to render the topology on openshift

I have deployed skydive operator on openshift and I am facing below problems. Please help me in resolving the issues.

1. The ui is taking too long time to load the topology and frequently browser says 'Page unresponsive' (using Google chrome and firefox).
2. Frequently I see connected/disconnected messages on the right hand top corner.
3. The agent running on the node where analyzer is running is connected to the analyzer and rest of the agents (daemon sets are unable to connect to the analyzers and the below is found in logs.

2020-08-23T18:30:51.434Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:33:02.506Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:35:13.578Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:37:24.650Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:39:35.722Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:41:46.794Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:43:57.866Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent

Skydive in OperatorHub

The goal is to contribute the skydive operator to the operator hub (https://operatorhub.io/contribute)

Initially we can use the operator-sdk generated operator from helm (https://github.com/operator-framework/operator-sdk/blob/master/doc/proposals/helm-operator.md)

Later we can develop a golang operator using kubebuilder (https://github.com/kubernetes-sigs/kubebuilder)

And going forward we could even make Skydive act like a k8s native application by creating CRDs (Custom Resource Definitions) to represent the SkydiveAnalyzer (one per cluster) and SkydiveAgent (one per node)

UI continuously renders the topology(connecting/disconnecting) on openshift platform (using skydive operator)

I have deployed skydive on Openshift platform using skydive operator. Once the instance of operator is installed I see the resources are continuously connecting/disconnecting. Any suggestions to sort out this issue?

Image should be built inside the Skydive CI

skydive-operator/deploy/operator.yaml

Line 19 in 779d239

image: quay.io/sacloud/skydive-op:v0.0.2