Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Document using Consul Connect integration with Consul ACLs

See original GitHub issue

https://www.getambassador.io/user-guide/consul-connect-ambassador/ does not include any info on how to run the Consul connector with ACLs enabled and it’s not obvious what needs to be done to do so. This process should be documented on that page.

Here’s how I’ve done it, but I’m not sure if it’s the most correct approach:

# Add to https://getambassador.io/yaml/consul/ambassador-consul-connector.yaml
        env:
        - name: CONSUL_HTTP_TOKEN
          valueFrom:
            secretKeyRef:
              key: token
              name: <helm release name>-consul-bootstrap-acl-token

It seems like there should be a better way that using the bootstrap token.

Issue Analytics

State:
Created 4 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

3reactions

stale[bot]commented, May 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

2reactions

stale[bot]commented, Jul 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.