Explore >> Select a destination
|
You are here 
|
cilium.io | ||
| | | | |
isovalent.com
|
|
| | | | | In this tutorial, you will learn how to enable Enterprise features (Layer-3, 4 & 7 policies, DNS-based policies, and observe the Network Flows using Hubble-CLI) in an Azure Kubernetes Service (AKS) cluster running Isovalent Enterprise for Cilium. | |
| | | | |
www.codecentric.de
|
|
| | | | | Integrating Cilium and Dapr for a powerful infrastructure to simplify service management and boost scalability - the next generation of distributed applications | |
| | | | |
jreypo.io
|
|
| | | | | In the article about Kubernetes on ACS I briefly touched the topic of Kubernetes Ingress, originally I was going to made a post about Ingress however I thought it woud be better to explain the different methods to expose a Kubernetes based app and how are they implemented on Azure. | |
| | | | |
sean.thrailkill.cloud
|
|
| | | If you're crazy like me and are running a Kubernetes cluster in your home then chances are you also have other computers running other services. In the past, I would have my storage server run Nginx for any internal services (meaning LAN only) and then used an ingress controller like Traefik or Nginx to serve traffic from inside my cluster to the internet. Recently, I thought that it might be better to also run my internal reverse proxy on something highly available should (God forbid) my storage server go down. So off to the internet I went looking. Turns out its actually surprisingly easy to accomplish this. | ||
