Back to basics: accessing Kubernetes pods

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • kubernetes-ingress

    NGINX and NGINX Plus Ingress Controllers for Kubernetes

    It's implementation-dependent and implementations offer different features, e.g., Nginx, Traefik, HAProxy, etc.

  • metallb

    A network load-balancer implementation for Kubernetes using standard routing protocols

    -- MetalLB

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  • traefik

    Discontinued The Cloud Native Application Proxy [Moved to: https://github.com/traefik/traefik] (by containous)

    It's implementation-dependent and implementations offer different features, e.g., Nginx, Traefik, HAProxy, etc.

  • kind

    Kubernetes IN Docker - local clusters for testing Kubernetes

    For the sake of the demo, I'll be using Kind:

  • haproxy-ingress

    HAProxy Ingress

    It's implementation-dependent and implementations offer different features, e.g., Nginx, Traefik, HAProxy, etc.

  • gateway-api

    Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

    In this post, I've described several ways to access pods outside the cluster: NodePort and LoadBalancer services and Ingress. For Ingress, you may have noticed that the ApisixRoute object is a proprietary CRD. To avoid it, Kubernetes aims to provide an abstraction; the CNCF is working on a Gateway API project.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts