Dynamically provision (V)IP, Load Balancer configuration and DNS alias for services deployed on containers platforms.
Interlook has a concept of "Providers" and "Provisioners", orchestrated by the "core".
Providers are connected to the containers platform and are responsible for detecting service deployment or deletion.
Provisioners are responsible for interacting with infra components like DNS server, IPAM tools and load balancers/reverse proxies.
The core receives add/delete events from the providers, injects them as workflow entry with a target state ("deployed" or "undeployed").
Then it ensures the relevant tasks are performed by the different "provisioners" (as defined in the workflow) to bring the service to the desired state.
Boris HUISGEN bhuisgen@hbis.fr
Michael CHAMPAGNE mch1307@gmail.com
``bash
VERSION=$(git log -n1 --pretty="format:%d" | sed "s/, /\n/g" | grep tag: | sed "s/tag: |)//g") &&
VERSION=$VERSION-$(git log -1 --pretty=format:%h) &&
CGO_ENABLED="0" GOARCH="amd64" GOOS="linux" go build -a -installsuffix cgo -o interlook -ldflags="-s -w -X github.com/interlook/interlook/core=$VERSION"