Gabriel de Oliveira Barbosa

I have just fall into this issue while testing the new URLrewrite filter on latest consul-k8s helm chart (v0.47.1). Managed to register routes in primary datacenter, but similar configs does...

Thank you guys, will test it right now.

> @codex70 @manobi version `0.48.0` is now available for the consul Helm chart and contains the code changes related to this issue ([changelog](https://github.com/hashicorp/consul-k8s/releases/tag/v0.48.0)) @nathancoleman Consul API gateway controller never becomes...

That would help with the troublesome implementation I have setup with Terraform and consul provider.

> If using ACLs, this must be the same name as the Pod's ServiceAccount. This is my current challenge, even having `active` and `preview` service account it's hard to sync...

That would solve the problem of waiting for pods created by custom resources.

Hi @tdgeery, using the same approach to get token from kubernetes secret and having the same issue while reading consul policies. Did you figure it out how to solve?

@nathancoleman I'll try this soon, thank you for sharing.

@nathancoleman I've tried with consul-k8s (0.49.0) and `hashicorppreview/consul-api-gateway:0.5-dev` but still: ``` 2022-10-02T00:09:03.658Z [ERROR] consul/certmanager.go:257: consul-api-gateway-server.cert-manager: error grabbing leaf certificate: error="Unexpected response code: 403 (rpc error making call: rpc error making...

Hi @nathancoleman The policy does exists and when the secondary datacenter was created there was already a registered `Gateway` in primary dc (v0.48.0). ``` apiGateway: enabled: true image: hashicorppreview/consul-api-gateway:0.5-dev managedGatewayClass:...