I am trying to helm upgrade consul from 1.15.0 to 1.16.2, how ever, the upgrade fails because there is already a cluster resource defenition for GatewayClass exists in default namespace. (I am installing consul in consul namespace). The existing Gateway Class is registered and managed by istio, and I would like to keep it that way. Is there a way in helm to disable GatewayFeautes? My primary usage for consul is only the kv engine acting as a backend for vault.
Hi @manibk31,
Welcome to the HashiCorp Forums!
If you are only using Consul for Vault KV Backend, you can set connectInject.enabled=false in your values file, so that Service Mesh-related components are not installed (which includes the API Gateway-related resources).
Could you please try this and see if it works for you?