{{- if eq .Values.envoy.service.type "LoadBalancer" }}
1. Get Contours's load balancer IP/hostname:

     NOTE: It may take a few minutes for this to become available.

     You can watch the status by running:

         $ kubectl get svc {{ include "common.names.fullname" . }}-envoy --namespace {{ .Release.Namespace }} -w

     Once 'EXTERNAL-IP' is no longer '<pending>':

         $ kubectl describe svc {{ include "common.names.fullname" . }}-envoy --namespace {{ .Release.Namespace }} | grep Ingress | awk '{print $3}'

2. Configure DNS records corresponding to Kubernetes ingress resources to point to the load balancer IP/hostname found in step 1
{{- end }}
{{- if eq .Values.envoy.service.type "NodePort" }}
{{- if (and (not (empty .Values.envoy.service.nodePorts.https)) (not (empty .Values.envoy.service.nodePorts.http)))}}
1. Contour is listening on the following ports on the host machine:

     http - {{ .Values.envoy.service.nodePorts.http }}
     https - {{ .Values.envoy.service.nodePorts.https }}
{{- else }}
1. Contour has been started. You can find out the port numbers being used by Contour by running:

          $ kubectl describe svc {{ include "common.names.fullname" . }} --namespace {{ .Release.Namespace }}

{{- end }}

2. Configure DNS records corresponding to Kubernetes ingress resources to point to the NODE_IP/NODE_HOST
{{- end }}

{{ include "common.warnings.rollingTag" .Values.contour.image }}
{{ include "common.warnings.rollingTag" .Values.envoy.image }}
