This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
Controller certificate watch fails in secondary datacenter #361
Labels
type/bug
Something isn't working
Overview of the Issue
This issue is a contributing factor to #300.
The controller fails to initialize a watch on root certificates when starting up in a secondary datacenter. This is because the primary datacenter needs to be included when creating the watch but is not today.
consul-api-gateway/internal/consul/certmanager.go
Lines 215 to 217 in c35994b
Reproduction Steps
apiGateway.enabled: true
in values.yaml).kubectl logs ...
)Logs
Logs
Expected behavior
Controller successfully starts up (including cert watch initiated as part of startup)
Environment details
If not already included, please provide the following:
Additionally, please provide details regarding the Kubernetes Infrastructure, as shown below:
Additional Context
The text was updated successfully, but these errors were encountered: