Azure AKS : Ingress overview
4.7 هزار بار بازدید -
4 سال پیش
-
https://pachehra.blogspot.com/
https://docs.microsoft.com/en-us/azur...
When you create a LoadBalancer type Service, an underlying Azure load balancer resource is created. The load balancer is configured to distribute traffic to the pods in your Service on a given port. The LoadBalancer only works at layer 4 - the Service is unaware of the actual applications, and can't make any additional routing considerations.
Ingress controllers work at layer 7, and can use more intelligent rules to distribute application traffic. A common use of an Ingress controller is to route HTTP traffic to different applications based on the inbound URL.
Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource.
An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name based virtual hosting.
In order for the Ingress resource to work, the cluster must have an ingress controller running.
Unlike other types of controllers which run as part of the kube-controller-manager binary, Ingress controllers are not started automatically with a cluster.
An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically uses a service of type Service.Type=NodePort or Service.Type=LoadBalancer.
Terraform with Azure : Count , length...
Terraform with Azure : Workspaces
Terraform with Azure : Variables & In...
Terraform with Azure Part-1
Video
Video
AZ-300 Introductory Video
AZ-300 Configure Diagnostics settings...
AZ-300 Create Action Groups
AZ-300 Alerts and baseline resources
My name is Arun Pachehra and i am an IT Professional & a fitness enthusiast. Its been more than 12 years working with various technologies and now i am planning to share with you all. As per plan i am going to publish the entire Az 300 series first and if things would go as planned then a lot of stuff would come your way including Q&A , Production issues and various interesting stuff.
https://docs.microsoft.com/en-us/azur...
When you create a LoadBalancer type Service, an underlying Azure load balancer resource is created. The load balancer is configured to distribute traffic to the pods in your Service on a given port. The LoadBalancer only works at layer 4 - the Service is unaware of the actual applications, and can't make any additional routing considerations.
Ingress controllers work at layer 7, and can use more intelligent rules to distribute application traffic. A common use of an Ingress controller is to route HTTP traffic to different applications based on the inbound URL.
Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource.
An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name based virtual hosting.
In order for the Ingress resource to work, the cluster must have an ingress controller running.
Unlike other types of controllers which run as part of the kube-controller-manager binary, Ingress controllers are not started automatically with a cluster.
An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically uses a service of type Service.Type=NodePort or Service.Type=LoadBalancer.
Terraform with Azure : Count , length...
Terraform with Azure : Workspaces
Terraform with Azure : Variables & In...
Terraform with Azure Part-1
Video
Video
AZ-300 Introductory Video
AZ-300 Configure Diagnostics settings...
AZ-300 Create Action Groups
AZ-300 Alerts and baseline resources
My name is Arun Pachehra and i am an IT Professional & a fitness enthusiast. Its been more than 12 years working with various technologies and now i am planning to share with you all. As per plan i am going to publish the entire Az 300 series first and if things would go as planned then a lot of stuff would come your way including Q&A , Production issues and various interesting stuff.
4 سال پیش
در تاریخ 1399/04/15 منتشر شده
است.
4,728
بـار بازدید شده