Overview:
Kubernetes uses services abstraction in order to expose app to the outside world. When you create a container app for K8s in Murano, it will automatically create a svc if you click “visible from outside” radio button.
We noticed that inside of K8s all services created by murano has following naming convention: “svc-random”.
Reference: https://github.com/openstack/murano-apps/blob/master/Docker/Kubernetes/KubernetesCluster/package/Classes/KubernetesCluster.yaml#L223
This makes very hard to understand which services belong to which application when you do verification with “kubectl get services” command.
We suggest that services name convention will change to “applicationName-random”.
Same should be for Deployments if those will be introduced to Murano Apps.
Actual behavior:
Services for app has created by Murano K8s App is “svc-random”
Proposed behavior:
Services for app has created by Murano K8s App is “applicationName-random”
Or
Services for app has created by Murano K8s App should be called “applicationName” but
Attached logs:
ubuntu@murano-sjevlirvfp6t34i-kube-1-jah3qodpxsq2:~/go/src/github.com/askcarter/workshop-in-a-box/bundles/kubernetes-101/kubernetes$ kubectl get services
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc-aeggkirvjf3va4j 11.1.81.239 <none> 80/TCP 1d
svc-fuoknirx98k2f4o 11.1.248.106 <none> 1029/TCP 1h
svc-hsifairx9857z4n 11.1.207.192 <none> 1028/TCP 1h
svc-qjdprirx93fhh4l 11.1.53.140 <none> 1026/TCP 1h
svc-qxfelirx91q304k 11.1.96.49 <none> 1025/TCP 1h
svc-vhggjirx97o6x4m 11.1.186.77 <none> 1027/TCP 1h
Fix proposed to branch: master
Review: https:/