Please vote on this issue by adding a š reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
When setting up Federation in between two kubernetes getting the following error message
atacenter" 2023-06-01T10:16:23.455Z [WARN] agent: (WAN) couldn't join: number_of_nodes=0
error=
1 error occurred:
* Failed to join 192.0.2.2:8302: dial tcp ->158.101.35.180:443: i/o timeout
2023-06-01T10:16:23.455Z [WARN] agent: Join cluster failed, will retry: cluster=WAN retry_interval=30s
When evaluate the ip address of the peers in the generated secret object the IP address is incorrect,
this is happend only when deploying the helm to an existing namespace , when deploying the helm to new namespace it works fine.
Reproduction Steps
In order to reproduce try deploy the helm chart into a namespace that is allready existing
kubectl delete secret -n management federation-consul-federation
helm install dc1 hashicorp/consul -f ~/git/Kube-XXX/federation/dev-config-cluster1.yaml -n management
kubectl logs -n management federation-consul-server-0 -f
Community Note
Overview of the Issue
2023-06-01T10:16:23.455Z [WARN] agent: Join cluster failed, will retry: cluster=WAN retry_interval=30s
When evaluate the ip address of the peers in the generated secret object the IP address is incorrect,
kubectl get secret -n management federation-consul-federation -o yaml | grep -i serverConfigJson | awk '{ print $2 }' | base64 -d
this is happend only when deploying the helm to an existing namespace , when deploying the helm to new namespace it works fine.
Reproduction Steps
In order to reproduce try deploy the helm chart into a namespace that is allready existing kubectl delete secret -n management federation-consul-federation helm install dc1 hashicorp/consul -f ~/git/Kube-XXX/federation/dev-config-cluster1.yaml -n management kubectl logs -n management federation-consul-server-0 -f
Helm Values: `global: name: federation-consul datacenter: dc1
tls: enabled: true
federation: enabled: true createFederationSecret: true
acls: manageSystemACLs: false createReplicationToken: false
gossipEncryption: autoGenerate: false
connectInject: enabled: true
meshGateway: enabled: true `
Logs
Expected behavior
Expecting to have the IP set properly .
Environment details
Additional Context