Nathan Coleman

Thanks for reporting @krarey! This is an issue with the Helm chart that the API Gateway team will work on addressing

@manobi I believe it's just a matter of configuring the `acl-auth-method` and `primary-datacenter` appropriately when deploying the API Gateway controller into a secondary datacenter. Please see the PR I just...

@codex70 #1462 will be included in the next release of consul-k8s, slated for this Thursday, September 1

@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))

Hi @codex70 the insufficient permissions issue described here is resolved by the combination of #1462 (merged + released) and #1481 (in code review). With the API Gateway controller running in...

Thanks @carlisia ! I think that makes this issue much more manageable

There was some relevant discussion between myself, @skriss and @robscott in https://github.com/kubernetes-sigs/gateway-api/pull/1158#discussion_r869537633. The spec doesn't specifically call for this to be set to `true` for a healthy state today. This...

The workaround for now is to create the workspace manually so that the pod can start up successfully

@codex70 @manobi I recorded a demo yesterday pulling together the 3 related PRs that will be included across the upcoming consul-k8s `v0.49.0` and consul-api-gateway `v0.5.0` releases to support Gateway per...

Hi @manobi :wave: I was able to get everything working w/ _fresh_ clusters/datacenters using `0.48.0` for the primary dc and `0.49.0` for the secondary dc. I do notice though that...