Jared Kirschner

Hi @nivdahan18, I have a few clarifying questions to help answer: - Are the services in the Consul service mesh? Or are they outside of the service mesh (just using...

If you're not using service mesh, follow @blake's guidance above. Your DNS query needs to be a SRV query for the weights to be returned. The DNS client is responsible...

Hi @usovamaria, I'm not personally familiar with the `agent` token having ever been used for service registrations from config files on agent startup/reload. My understanding is that the `default` token...

The version-specific upgrade details page states that `connect` is enabled by default as of Consul 1.14: https://developer.hashicorp.com/consul/docs/upgrading/upgrade-specific#consul-1-14-x As you noted, you can explicitly disable `connect` by setting `connect.enabled = false`....

@vyanamandra : Just checking, is this ready for review? Or is there anything else you're finishing up first? Thanks for expanding this from the initial PR!

Hi @n-marton, This looks very interesting - thank you for proposing this contribution! To help me better understand, can you share an example scenario with before/after that shows the importance/benefits...

Hi @n-marton, Thank you for the thoughtful reply. I've discussed this with the team and wanted to follow up. In short, we acknowledge that there's an underlying need here that...

@thevilledev : Is the PR description still accurate? I noticed that it mentions: > Remove the token field from the Consul configuration file. We don't want to remove the token...

@thevilledev : What do you think about also adding support in this PR for pulling the Vault address from the `VAULT_ADDR` environment variable? I realize that's probably a less meaningful...

> One edge case to consider: this change could potentially break setups of users who already had VAULT_* environment variables since those will now cause the CA to error on...