consul-template | Template rendering , notifier , and supervisor for @ | Configuration Management library

I have a consul server running on https://dev.example.com/ on which I store configurations as below:

consul key name = dev

consul key value = some yaml data

kubernetes configMap value some yaml data --> ( this is in sync with consul data )

what I want to do is as soon as I change something in some yaml data, the values should be automatically reflected in configMap and pod should be reloaded automatically to capture new values.

I have tried envconsul but it only picks keys with one value.

I tried consul-template but did not find any good working example.

I am very new to consul. I just want to load my environment variables from consul kv using consul-template. I have an consul kv entry having key "iamdbusername". I want to assign its value in an environment variable IAM_DB_USER with the help of consul-template. My application is using the environment variable IAM_DB_USER for getting the database user name.

Any clue in this will be very helpful for me.

Thanks!!!

I'm trying to figure out which tools from GKE stack I should apply to my use case which is a dynamic deployment of stateful application with dynamic HTTP endpoints.

Stateful in my case means that I don't want any replicas and load-balancing (because the app doesn't scale horizontally at all). I understand though that in k8s/gke nomenclature I'm still going to be using a 'load-balancer' even though it'll act as a reverse proxy and not actually balance any load.

The use case is as follows. I have some web app where I can request for a 'new instance' and in return I get a dynamically generated url (e.g. http://random-uuid-1.acme.io). This domain should point to a newly spawned, single instance of a container (Pod) hosting some web application. Again, if I request another 'new instance', I'll get a http://random-uuid-2.acme.io which will point to another (separate), newly spawned instance of the same app.

So far I figured out following setup. Every time I request a 'new instance' I do the following:

• create a new Pod with dynamic name app-${uuid} that exposes HTTP port
• create a new Service with NodePort that "exposes" the Pod's HTTP port to the Cluster
• create or update (if exists) Ingress by adding a new http rule where I specify that domain X should point at NodePort X

The Ingress mentioned above uses a LoadBalancer as its controller, which is automated process in GKE.

A few issues that I've already encountered which you might be able to help me out with:

1. While Pod and NodePort are separate resources per each app, Ingress is shared. I am thus not able to just create/delete a resource but I'm also forced to keep track of what has been added to the Ingress to be then able to append/delete from the yaml which is definitely not the way to do that (i.e. editing yamls). Instead I'd probably want to have something like an Ingress to monitor a specific namespace and create rules automatically based on Pod labels. Say I have 3 pods with labels, app-1, app-2 and app-3 and I want Ingress to automatically monitor all Pods in my namespace and create rules based on the labels of these pods (i.e. app-1.acme.io -> reverse proxy to Pod app-1).
2. Updating Ingress with a new HTTP rule takes around a minute to allow traffic into the Pod, until then I keep getting 404 even though both Ingress and LoadBalancer look as 'ready'. I can't figure out what I should watch/wait for to get a clear message that the Ingress Controller is ready for accepting traffic for newly spawned app.
3. What would be the good practice of managing such cluster where you can't strictly define Pods/Services manifests because you are creating them dynamically (with different names, endpoints or rules). You surely don't want to create bunch of yaml-s for every application you spawn to maintain. I would imagine something similar to consul templates in case of Consul but for k8s?

I have a react app that I want to deploy to kubernetes using a docker file and host it using nginx. My Dockerfile looks like this

I've just inherited an Nginx proxy/app server setup that makes use of Consul and Consul Template for service discovery and registration. The Nginx proxy has a config file with an entry like this to register the downstream app servers:

We have an nginx conf file that is being produced with consul-template for 2000+ services, running Consul 1.6.1.

We're trying to upgrade to Consul 1.7.2 and running into an issue where consul-template DDoSes Consul node agent.

Node/client agent v1.6.1 works fine, but node/client agent v1.7.2 starts refusing connections from consul-template.

The template in question (simplified version) is:

My Kubernetes Deployment is composed like this:

can someone tell me the error in the Dockerfile given below: I am trying to follow instructions given in this repo: https://github.com/anthcourtney/docker-consul-template-haproxy