In the ServiceSpec yaml below, we're using type: nodePort though it's not the type of we want to expose an app in this post. So, let's expose our pods using Services (e2e-service.yaml). As we can see from the deployment yaml, the port that the application is running on is 8080: "note that containerPort: 8080". Nginx-ingress-controller-8566746984-9bxbh 1/1 Running 0 2mĪt this time, though the e2e app container is running, we cannot access the app. Kubernetes-dashboard-6f4cfc5d87-7f8vl 1/1 Running 5 30m Kube-scheduler-minikube 1/1 Running 2 30m Kube-controller-manager-minikube 1/1 Running 0 11m Kube-apiserver-minikube 1/1 Running 0 11m Kube-addon-manager-minikube 1/1 Running 2 29m It creates an "nginx-ingress-controller" pod in the "kube-system" namespace.Īfter enabled the ingress, we can see that the nginx-ingress-controller is in the list of pods:Ĭoredns-c4cffd6dc-xjr2v 1/1 Running 2 30mĭefault-http-backend-544569b6d7-fqczz 1/1 Running 0 2m The Ingress Controller is created when we run the "minikube addons enable ingress". Kubernetes-dashboard-6f4cfc5d87-7f8vl 1/1 Running 5 25m Kube-scheduler-minikube 1/1 Running 2 26m Kube-controller-manager-minikube 1/1 Running 0 7m Kube-addon-manager-minikube 1/1 Running 2 25m Kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100Ĭoredns-c4cffd6dc-xjr2v 1/1 Running 2 25m Kubectl is now configured to use the cluster. Starting local Kubernetes v1.10.0 cluster.
We'll use Minikube which runs a single-node (or multi-node with minikube 1.10.1 or higher) Kubernetes cluster inside a VM on our laptop:
If we use a Cloud provider's load balancer, we don't have to implement it by ourselves. The Ingress controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure our edge router or additional frontends to help handle the traffic: Services, Load Balancing, and Networking/ Traffic routing is controlled by rules defined on the Ingress resource.Īn Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting.įor more details on Ingress, please check out Kubernetes Documentation/ The Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. The following diagram shows how we can access using the Kubernetes service:Īs we can see, we use but what we want is to access our pod via This is where the Ingress comes into the picture: It is built around the Kubernetes Ingress resource, using a ConfigMap to store the NGINX configuration.
0 kommentar(er)
