Determining ingress host availability across Kubernetes clusters

Lets say you have two apps available at a.b.com and x.y.com and you have 3 available Kubernetes it could potentially be deployed on, clusterA, clusterB and clusterC. Generally upstream from your cluster LoadBalancers you will have another cloud load balancer device or you are just using some sort of DNS service to control what cluster LoadBalancer IPs are relevant for each application at any given time. To … Continue reading Determining ingress host availability across Kubernetes clusters

Docker container peer IP discovery with Swarm services

  When running applications deployed as a docker "service" within Docker Swarm (post 1.12 swarm mode), often those application's have the need to discover their peer containers for purposes such as forming a cluster. Similar to "service discovery", I'll just use the term "peer discovery" for this use-case. The simple example is as follows: You … Continue reading Docker container peer IP discovery with Swarm services

Hazelcast discovery with Docker Swarm

After going through a lot of R&D of deploying Hazelcast enabled apps as Docker Containers, first starting on pre-Docker 1.12 (legacy swarm, w/ mgrs/agents etc), with Registrator and Consul, ended up creating the hazelcast-consul-discovery-spi (available on GitHub). This served its purpose well, but as Docker evolved and post 1.12 "swarm mode" came out with the … Continue reading Hazelcast discovery with Docker Swarm

Docker container IP and port discovery with Consul and Registrator

Do you use Docker? Does your containerized app have the need to discover both its own IP and one or more mapped ports? How can another container access my exposed ports and how can I do the same of my peers? As it stands today, simple self discovery of your container's accessible IP and one … Continue reading Docker container IP and port discovery with Consul and Registrator