-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about challenge 5: info missing from provided yaml file? #58
Comments
@ntrogh any pointers on this one? I am thinking about the very same thing. |
I think so too, moreover I couldn't apply secret in consul-federation.yaml (base64 invalid data)... maybe I have done a wrong procedure? it's my first experience with consul :-) |
Doh, this was my PEBKAC. I was juggling multiple versions of the secret file with some being placeholders until I created the central cluster. Must have copied the wrong file in the end :( I've given Nick the correct files now, so should be fixed soon. Sorry! |
Updated file is now available! |
@ntrogh can you update the challenge to have the federation secret of the new central cluster? |
Hi,
To federate our own Consul clusters with the primary datacenter, don't we need the rest of the configuration (under
data
block) in consul-federation.yaml?The text was updated successfully, but these errors were encountered: