馃憢 Welcome! This is Saber’s blog!
- Saber is a DevOps enginner who’s in love with Linux, networking, Golang and Kubernetes!
- Here I’ll share what I learned in my career path, what I’ve faced in the way and other docs and stuff.
Getting started with HTTPProxy basics, Contour's alternative API for Ingress
From official doc, the goal of the HTTPProxy Custom Resource Definition (CRD) is to expand upon the functionality of the Ingress API to allow for a richer user experience as well addressing the limitations of the latter鈥檚 use in multi tenant environments. Key HTTPProxy Benefits Safely supports multi-team Kubernetes clusters, with the ability to limit which Namespaces may configure virtual hosts and TLS credentials. Enables including of routing configuration for a path or domain from another HTTPProxy, possibly in another Namespace....
Install and setup Contour ingress controller
Today we鈥檒l install and setup Contour ingress controller. But what is Contour? From what official docs say, Contour is an ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer. Contour supports dynamic configuration updates out of the box while maintaining a lightweight profile. Contour APIs Contour supports multiple configuration APIs in order to meet the needs of as many users as possible:...
Setup TLS Ingress rule using Contour ingress controller
Today we鈥檒l setup an ingress rule using Contour. You can follow this guide to setup Contour ingress controller on your K8s cluster. First, we鈥檒l create a simple Ingress rule to handle plain HTTP requests to our service for us. Simple HTTP Ingress apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: http-ingress spec: ingressClassName: contour rules: - host: "example.org" http: paths: - backend: service: name: app-svc port: number: 8181 path: / pathType: Prefix By applying this Ingress rule, Contour will be notified and will command Envoy to setup required configuration on each Envoy pod to be able to redirect traffic destined to example....
Setup your own local overlay network from scratch!
Want to know how Docker containers work? We鈥檙e gonna find out! Today we鈥檙e going to simulate container networking. We鈥檒l do this with magic of Linux namespaces, virtual ethernet devices, bridge devices, and iptables. Note You鈥檒l need root access to be able to run given commands. First, we鈥檒l create two network namespace for containers container-1 and container-2 named c1 and c2. This command will create two seperate namespaces which have their own interfaces and routing tables:...