Answers: <p>It's would be better if you will use <code>ClusterIP</code> type as a service than apply <code>Ingress</code> resource on it</p>
  <p><a href="https://kubernetes.io/docs/concepts/services-networking/ingress/#single-service-ingress" rel="noreferrer">https://kubernetes.io/docs/concepts/services-networking/ingress/#single-service-ingress</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2020-07-07T19:19:07.587Z
Answers: 2020-07-07T19:19:07.587Z
Answers: Hakob
Body: <p>I used google compute engine to setup a Self Managed Kubernetes, While exposing ingress service via NodePort/LoadBalancer/EnternalIP, it is using default 30000 port range, But I want to expose it on 80 and 443 to the outer world. Please suggest How can I do that?</p>
  
Tags: <kubernetes><google-cloud-platform><ingress><google-kubernetes-engine>
Title: How can I expose Ingress service on 80 and 443 to the outer world
UserDisplayName: Radheyshyam Sen
ThreadText: # How can I expose Ingress service on 80 and 443 to the outer world
  
  (Asked by: username_0 on 2020-07-04)
  
  I used google compute engine to setup a Self Managed Kubernetes, While exposing ingress service via NodePort/LoadBalancer/EnternalIP, it is using default 30000 port range, But I want to expose it on 80 and 443 to the outer world. Please suggest How can I do that?
  
  **Tags:** kubernetes, google-cloud-platform, ingress, google-kubernetes-engine
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-07-07. Score: 6 | Accepted answer
  
  It's would be better if you will use `ClusterIP` type as a service than apply `Ingress` resource on it
  
  <https://kubernetes.io/docs/concepts/services-networking/ingress/#single-service-ingress>
  
  
  ---
  
  