Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 in progress · Last activity 8y ago
See all on GitHub →
Hi, I’m wondering if you experience the same issue I have. If two of the 3 pods get killed and recreated they won’t be able to rejoin the cluster and the UI won’t respond. I checked the logs and all 3 pods trying to elect a leader using the old IPs of the two dead pods instead of the new pod IPs. I spent days trying to figure out why. If you could provide any assistance I would greatly appreciate it. Thanks.
Recent fixes
The only hiccup I had was getting gcloud set up. For a fresh install, I didn't have a default project or zone set up, so eventually I found the use of the config command to set defaults that let me precede. I added what I used for others. Hope it is useful!
Given that the Google Cloud Free Trial only offers 8 CPUs in a single region, it's impossible to run the entire cluster with 2-CPU machines with a new account. I changed the machine types from to to reduce CPUs from 2 to 1 for each machine, and halved the resources in the files to match. I did have to add a fourth node to the in the nomad cluster to account for all running Nomad containers. I didn't dig too deep to figure out if there's a better layout, but given that all the services can run with reduced resources, I think this is a good start. Please let me know if you have any issues with my proposed changes here. Having limited experience with k8s and virtually none with Vault, Consul, and Nomad, I'm eager to learn more.
Structured data for AI agents
Repository: kelseyhightower/nomad-on-kubernetes. Description: Tutorial on running Nomad on Kubernetes. Stars: 355, Forks: 49. Primary language: Shell. Languages: Shell (66.6%), Go (20.9%), HCL (12.6%). License: Apache-2.0. Open PRs: 1, open issues: 1. Last activity: 8y ago. Community health: 42%. Top contributors: kelseyhightower, ianmiell, mehzer.