search

emissary-ingress / emissary

open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
https://www.getambassador.io
Apache License 2.0
4.35k stars 681 forks source link

Document using Consul Connect integration with Consul ACLs #2079

Open HT154 opened 4 years ago

HT154 commented 4 years ago

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.

stale[bot] commented 4 years ago

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.

HT154 commented 4 years ago

bump

stale[bot] commented 4 years ago

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.

HT154 commented 4 years ago

nope

stale[bot] commented 4 years ago

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.

lawliet89 commented 3 years ago

Bump.

Same issue with TLS for Consul Agents.

stale[bot] commented 3 years ago

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.

lawliet89 commented 2 years ago

Bump