kong kubernetes ingress

The content of this section: Service Discovery and load balancing Ingress Combat First, service discovery and load balancingIn the previous installation deployment Kubernetes cluster, it was simple to demonstrate that pod and Service,kubernetes implemented service discovery and load balancing for containers within the

Kubernetes about the service exposure is mainly through the Nodeport way, through the binding minion host of a port, then the pod request forwarding and load balancing, but this way the defect is The service may have many, if each is bound to a node host port, the host needs to open the perimeter of a heap of ports to make services calls, management confusion Cannot apply firewall rules required by many companies The ideal way is thr

[TOC]DescriptionThere is no detailed explanation of the Kubernetes's service exposure and Traefik's principles. The Traefik principle can be consulted in the official documentation: https://docs.traefik.io/, This document can also be consulted about the service exposure of kubernetes and the rationale for using Traefik as a kubernetes ingress: https://mritd.me/20

Services deployed by users on Kubernetes typically run on private networks, and pod and service provide parameters such as Hostport,nodeport to expose these service ports to K8S nodes for user access. There are obvious drawbacks to this approach:1) Easy to occupy excessive host port;2) service ports exposed to multiple hosts increasing the difficulty of firewalls and security configuration3) The default hostport,nodeport mode does not function as load

ObjectiveIngress is a way to expose the internal service of a k8s cluster, and user-edited profiles define a ingress resource to enable external network access to the intranet service.Ingress Controller is to manage all Ingress objects, ingress controller inside is actually an nginx container, when Ingress controll by

1, Ingress Components Introduction Ingress solves the problem of the domain name and service after the new service is added, basically a Ingress object, which is loaded by creating and updating with Yaml. Ingress Controller is to ingress this change to generate

:88Targetport:80SelectorApp:nginx[Email protected] ~]# Kubectl create-f Nginx-service.yaml[email protected] ~]# cat Ingress-nginx.yamlApiversion:extensions/v1beta1Kind:ingressMetadataName:nginxserviceNamespace:ingress-nginxSpecRules-Host:test.iohttpPaths-Path:/Backend:Servicename:nginx-serviceServiceport:80-Path:/# backend:# Servicename:kubernetes-dashboard# serviceport:80[Email protected] ~]# Kubectl create-f Ing