Can't connect to service created with kubectl when k8s cluster first deployed

[Craig Peters]

Three possible bugs:
 1. Initially unable to route data to a service created via kubectl, but can after doing a deploy of a service via Murano UI
 2. Manually added security group gets removed when Murano UI used to deploy service (but only the first time)
 3. Delete pod via Murano UI doesn't delete pod, service, or deployment

Steps to reproduce:
1. Create a Kubernetes cluster
2. Add Ingress for port 9000 to security group
3. With kubectl create nginx deployment and expose service on port 9000
[bug 1] 4. Curl fails to be able to get data from nginx from gateway on port 9000
5. Use Murano UI to deploy Nginx (which automatically exposes on port 80 - should add a feature to ask which port to use)
6. Curl get’s nginx data from port 80
7. Curl fails to get nginx data from port 9000
[bug 2] 8. Check security group, find that the Ingress rule for port 9000 was removed
9. Again, add ingress rule for port 9000
10. Curl gets nginx data from port 9000
11. Delete Kubernetes pod (but not Docker nginx) from Murano UI and deploy changes
[bug 3?] 12. Curl port 80 - still running
13. Check that the Murano created pod and service still exist
14. Delete Docker nginx from Murano UI
15. Check and the pod and service are now deleted
16. Check that Ingress rule for port 9000 still exists
17. Do another deploy... and this time the Ingress rule is NOT deleted

See attached video