Comments on: Kubernetes Multicluster with Kind and Submariner

By: WenDwo

WenDwo — Wed, 22 Feb 2023 02:28:54 +0000

Here were the results of executing ‘subctl join’.
root@c1-control-plane:~# subctl join broker-info.subm –natt=false
✓ broker-info.subm indicates broker is at https://c1-control-plane:6443
✓ Discovering network details
Network plugin: generic
Service CIDRs: [10.110.0.0/16]
Cluster CIDRs: [10.240.0.0/16]
There are 1 node(s) labeled as gateways:
– c1-worker
✓ Retrieving the gateway nodes
✓ Gathering relevant information from Broker
✓ Retrieving Globalnet information from the Broker
✓ Validating Globalnet configuration
✓ Deploying the Submariner operator
✓ Created operator namespace: submariner-operator
✓ Created operator service account and role
✓ Created submariner service account and role
✓ Created lighthouse service account and role
✓ Creating SA for cluster
✓ Connecting to Broker
✗ Deploying submariner
✗ Submariner deployment failed: error creating Submariner resource: error creating resource anew: timed out waiting for the condition
✗ Error deploying the Submariner resource: Submariner deployment failed: error creating Submariner resource: error creating resource anew: timed out waiting for the condition

subctl version: v0.14.1

By: WenDwo

WenDwo — Wed, 22 Feb 2023 02:21:25 +0000

Thanks for your promptly replying.
I found the SA was created by Submariner Operator as follows.
$ kubectl get sa -n submariner-operator
NAME SECRETS AGE
default 0 18h
submariner-diagnose 1 18h
submariner-gateway 1 18h
submariner-globalnet 1 18h
submariner-lighthouse-agent 1 18h
submariner-lighthouse-coredns 1 18h
submariner-networkplugin-syncer 1 18h
submariner-operator 1 18h
submariner-routeagent 1 18h

Here were some portions of error message from Submariner Operator.
2023-02-22T01:49:57.744Z INF ..riner_controller.go:144 ..troller_submariner Submariner is being deleted
2023-02-22T01:49:57.879Z ERR .._networkdiscovery.go:40 ..troller_submariner Error trying to discover network error=”error listing the Daemonsets: daemonsets.apps is forbidden: User \”system:serviceaccount:submariner-operator:submariner-operator\” cannot list resource \”daemonsets\” in API group \”apps\” in the namespace \”kube-system\””
2023-02-22T01:49:57.880Z INF .._networkdiscovery.go:50 ..troller_submariner No cluster network discovered
2023-02-22T01:49:57.880Z INF .._networkdiscovery.go:85 ..troller_submariner No detected CIDR type=Cluster
2023-02-22T01:49:57.880Z INF .._networkdiscovery.go:85 ..troller_submariner No detected CIDR type=Service
2023-02-22T01:49:57.880Z ERR ..oller/controller.go:326 Reconciler error error=”error discovering cluster network: error listing the Daemonsets: daemonsets.apps is forbidden: User \”system:serviceaccount:submariner-operator:submariner-operator\” cannot list resource \”daemonsets\” in API group \”apps\” in the namespace \”kube-system\”” controller=submariner-controller controllerGroup=submariner.io controllerKind=Submariner name=submariner namespace=submariner-operator reconcileID=559d9edd-404c-4f1e-9ed8-2f044fd176b8 submariner={“name”:”submariner”,”namespace”:”submariner-operator”}

I am very appreciated for giving some ideas or suggestions.

By: piotr.minkowski

piotr.minkowski — Tue, 21 Feb 2023 13:58:40 +0000

In reply to WenDwo. It seems you need to create a role and assign it to the SA submariner-operator to allow view daemonset objects. But it is quite strange - I didn't have to do it and operator should create it automatically

By: WenDwo

WenDwo — Tue, 21 Feb 2023 03:46:53 +0000

Hi, it’s the first time to try the Submariner project for me. I am following your procedures to setup the test environment on Ubuntu 20.04 Server. But I am stuck in deploying Submariner.
I entered the container of ‘c1-control-plane’ and modified /etc/kubernetes/admin.conf for adding the context of ‘kind-c2’. I copied the sections of ‘clusters’, ‘contexts’, ‘users’ from local ‘.kube/config’ and inserted into the ‘admin.conf’.
After executing ‘subctl deploy-broker’, the broker-info.subm file was created. But ‘subctl join broker-info.subm –natt=false –clusterid kind-c1’ timed out for the error message ‘error discovering cluster network: error listing the Daemonsets: daemonsets.apps is forbidden: User \”system:serviceaccount:submariner-operator:submariner-operator\” cannot list resource \”daemonsets\” in API group \”apps\” in the namespace \”kube-system\”‘.
I am very appreciated for giving some ideas or suggestions.

By: piotr.minkowski

piotr.minkowski — Sat, 10 Jul 2021 22:37:02 +0000

In reply to Fabio Almeida Caetano. Thanks :)

By: Fabio Almeida Caetano

Fabio Almeida Caetano — Sat, 10 Jul 2021 12:01:58 +0000

I’m a beginner in Kubernetes, what I saw were examples with 1 cluster in the desktop environment. I will try to create this environment. Very cool article

By: piotr.minkowski

piotr.minkowski — Fri, 09 Jul 2021 10:40:33 +0000

In reply to Kunalsing. Thanks :)

By: Kunalsing

Kunalsing — Fri, 09 Jul 2021 04:08:55 +0000

This is awesome