Search Results for "dns"

libcluster provides automatic cluster formation and node discovery for Erlang/Elixir applications, removing the manual steps typically required to connect distributed nodes. It ships with multiple pluggable strategies—such as DNS polling, Kubernetes integration, EC2 metadata/tag discovery, UDP gossip, and EPMD helpers—so you can adapt clustering to your runtime environment. The library supervises a topology process that continually discovers peers and joins or prunes nodes as they become available or disappear. Its design embraces OTP principles: strategies implement a behavior, can be composed, and run under supervision for resilience. libcluster also emits events on nodeup/nodedown, allowing applications to react (for example, rebalance work or update registries) when membership changes. ...

...Participating clusters should be provisioned into a single AWS account, within a single AWS region. Install the The CoreDNS multicluster plugin into each participating cluster. The multicluster plugin enables CoreDNS to lifecycle manage DNS records for ServiceImport objects. The controller must have sufficient IAM permissions to perform required Cloud Map operations. Grant IAM access rights AWSCloudMapFullAccess to the controller Service Account to enable the controller to manage Cloud Map resources.

...The tool is built to show how you can write Kubernetes controllers, use third-party resources, and react to changes in the API via watches and reconciliation loops. It supports DNS-01 challenge flows for ACME, allowing you to validate domain ownership and provision certificates automatically. It also integrates with Secrets and Ingress resources so you can consume the certificates in your applications easily. Although the project is primarily a demonstration or teaching project, it laid groundwork for more mature certificate controllers in the Kubernetes ecosystem.

...Once installed the script can be used for keeping version controlled Chronos job definitions up-to-date with a Chronos instance. Install DCOS CLI and configure for use "inside the cluster" with configured master nodes. The configuration relies on Mesos DNS to provide the Mesos master and Marathon endpoints.