|
You are here |
api7.ai | ||
| | | | |
jreypo.io
|
|
| | | | | In a previous article about exposing services in Azure Kubernetes Services I briefly touched on the Gateway API topic. This article is a first follow up on that one, it provides a deep dive into the Gateway API: what it is, why it exists, how it works, and what it enables for Kubernetes users. In the next one I will go deeper in the differences between the two main Ingress solutions in Azure, Azure Application Gateway Ingress Controller (AGIC) and Application Gateway for Containers (AGC). | |
| | | | |
blog.nobugware.com
|
|
| | | | | Manages Envoy Proxy with Envoy Gateway in Kubernetes | |
| | | | |
navendu.me
|
|
| | | | | A hands-on tutorial on using the new Kubernetes Gateway API with Apache APISIX Ingress. | |
| | | | |
arveknudsen.com
|
|
| | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. This is generally known as the ELK stack, which stands for Elasticsearch, Logstash (precursor to Fluentd) and Kibana. | ||