or too much to do in 1 rodeo

Because somebody asked about it, we did show it off a little bit in today’s rodeo.

It’s something that’s been on my to do list for a very long time: make a video about how to do federation. It’s pretty easy, but only after you’ve seen it done once.

I need to just try that and perhaps other mastersvc parameters listed in docs

a la point #6 here https://open-docs.neuvector.com/deploying/kubernetes/#deploy-neuvector

I am doing this on-prim so deployed metallb and added IP pool range Have 2 x 3-nodes RKE2 clusters... So one will be Fed-Master and another Fed-Worker On Master NV is running, and added this yaml

apiVersion: v1
kind: Service
metadata:
  name: neuvector-service-controller-fed-master
  namespace: cattle-neuvector-system
spec:
  ports:
  - port: 11443
    name: fed
    protocol: TCP
  type: LoadBalancer
  selector:
    app: neuvector-controller-pod

On Worker, same setup as above except added this yaml

apiVersion: v1
kind: Service
metadata:
  name: neuvector-service-controller-fed-worker
  namespace: cattle-neuvector-system
spec:
  ports:
  - port: 10443
    name: fed
    protocol: TCP
  type: LoadBalancer
  selector:
    app: neuvector-controller-pod

After deploying above yamls, I see On Fed-Master Loadbalancer IP was added to svc and ports 11443 On Fed-Worker Loadbalancer IP was added to svc and ports 10443 On Master, in the UI - promoted that cluster and generated token On Worker, in the UI - pasted the token and for Controller server added LB IP address I have on Fed-Worker cluster But this results in time out with error:

let me do some digging