Closed MBOps closed 4 years ago
eveld
commented
4 years ago Hey, can you check if the consul-server-0 pod is outputting a message of 2020-06-27T12:30:55.358Z [INFO] agent: (WAN) joining: wan_addresses=[*.dc1/192.0.2.2]. I am running into this myself now, eventhough the values in the consul-federation file are correct. I have had this problem before, but that was all locally, so assumed it was something to do with my local setup.
eveld
commented
4 years ago OK, I figured it out. It was a combination of consul generating a key for gossip + terraform creating a gossip encryption key secret. In the end we were double base64-ing the gossip key, as I was inputting it as a variable into Terraform to create a central cluster.
I recreated the central cluster and given @ntrogh the new federation secret.
MBOps
commented
4 years ago Cool thanks for the update.
ntrogh
commented
4 years ago Thanks for participating in the #TerraformOnAzure coding challenges! We have attached your very special Astronaut Badger background, for you to use in all your upcoming video calls!
And to recognize you for your learning, you can collect your digital Azure Heroes badge on your mobile (you may need to install the Enjin wallet to collect it). Make sure to collect it today! https://beam.enjin.io/claim/d32599695c8c28cfc24820492080fac0
Keep on learning and sharing!
Greetings from the #TerraformOnAzure team, Suzanne, Floor, Erik & Nick
Please provide the following information for your submission:
What is your name? (First, Last)
Matt Boyd
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/MBOps/AzureTerraformChallenge
What Challenge is this for? (Challenge number between 1 and 5)
5
(Optional) Anything else we should know? e.g., language used, location, blog post?
Issues getting the federation working.. not sure if it was a config issue with the values.yaml. Got Consul working but only reporting my own deployment