Last 12 weeks · 0 commits
2 of 6 standards met
If the deployment has 3 replicas, the config sidecar is running three times (one time in each pod). When the Kubernetes config map is updated, inotify will trigger the config sidecar in each pod and it will execute the command 3 times in parallel. But already propagate the config to all the peers. I wonder if it can cause problem with messages. The config side car will also need to get the correct when starting.
Repository: kelseyhightower/hello-habitat. Description: Running Habitat based applications on Kubernetes tutorial. Stars: 18, Forks: 1. Primary language: Go. Languages: Go (86.7%), Shell (13.3%). License: Apache-2.0. Open PRs: 0, open issues: 1. Last activity: 9y ago. Community health: 42%. Top contributors: kelseyhightower.