Hi Nicolae,

I can confirm that the nginx ingress-controller list is correct & complete.

Rest looks good to me (comparing it to what I see in our lab environment), but someone else can confirm if its complete.

sabeel

From: Jascanu, Nicolae <nicolae.jascanu@intel.com>
Sent: Wednesday, May 13, 2020 2:50 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] List of services and deployments

Hi All,

The Sanity tests are checking the list of services and deployments.app. I need a confirmation that the below lists are correct and complete:

$ kubectl get services -n kube-system

NAME                               TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE

ic-nginx-ingress-controller        ClusterIP   10.101.3.127    <none>        80/TCP,443/TCP           3h32m

ic-nginx-ingress-default-backend   ClusterIP   10.104.95.91    <none>        80/TCP                   3h32m

kube-dns                           ClusterIP   10.96.0.10      <none>        53/UDP,53/TCP,9153/TCP   3h38m

tiller-deploy                      ClusterIP   10.98.131.226   <none>        44134/TCP                3h38m

$ kubectl get deployments.apps -n kube-system

NAME                               READY   UP-TO-DATE   AVAILABLE   AGE

calico-kube-controllers            1/1     1            1           3h39m

coredns                            1/1     1            1           3h39m

ic-nginx-ingress-default-backend   1/1     1            1           3h33m

rbd-provisioner                    1/1     1            1           3h6m

tiller-deploy                      1/1     1            1           3h39m

Regards,

Nicolae Jascanu, Ph.D.

TSD Engineering Manager

Internet Of Things Group

Galati, Romania