-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connector-inject pod crashing with GatewayClass error #2296
Comments
Could you try with Consul K8s 1.2 and Consul 1.16 to see if the latest GA release solves your issue? |
Will go ahead and close, as there has been no response. |
Seeing this crash in 1.2.2
consul server
this seems related somehow with server unhealthy quorum server ( rebooted all consul VMs) and after getting cluster stabilised found not way to make pod recover from that crash. deleting k8s deployments for gateway and connect-injector and redeploying fixes the issue although in my case i need to reconfigure the service mesh peering once again. This seems to only have caused issues on 1 side of the mesh |
Hi Guys!,
Im experiencing an issue with the connnector-inject pod where my pod crashes with the following error. Any help would be greatly appreciated.
Pod logs
`2023-06-07T15:59:19.740Z [INFO] consul-server-connection-manager: trying to connect to a Consul server
2023-06-07T15:59:19.841Z [INFO] consul-server-connection-manager: discovered Consul servers: addresses=[192.168.111.128:8502, 192.168.71.138:8502, 192.168.84.180:8502]
2023-06-07T15:59:19.842Z [INFO] consul-server-connection-manager: current prioritized list of known Consul servers: addresses=[192.168.111.128:8502, 192.168.71.138:8502, 192.168.84.180:8502]
2023-06-07T15:59:19.940Z [INFO] consul-server-connection-manager: connected to Consul server: address=192.168.111.128:8502
2023-06-07T15:59:19.941Z [INFO] consul-server-connection-manager: updated known Consul servers from watch stream: addresses=[192.168.71.138:8502, 192.168.84.180:8502, 192.168.111.128:8502]
2023-06-07T15:59:20.991Z INFO Waited for 1.041443747s due to client-side throttling, not priority and fairness, request: GET:https://192.168.0.1:443/apis/config.gatekeeper.sh/v1alpha1?timeout=32s
2023-06-07T15:59:22.640Z INFO controller-runtime.metrics Metrics server is starting to listen {"addr": "0.0.0.0:9444"}
2023-06-07T15:59:25.640Z ERROR setup unable to register field indexes {"error": "no matches for kind "GatewayClass" in version "gateway.networking.k8s.io/v1beta1""}
github.com/hashicorp/consul-k8s/control-plane/subcommand/inject-connect.(*Command).Run
/home/runner/work/consul-k8s/consul-k8s/control-plane/subcommand/inject-connect/command.go:466
github.com/mitchellh/cli.(*CLI).Run
/home/runner/go/pkg/mod/github.com/mitchellh/[email protected]/cli.go:260
main.main
/home/runner/work/consul-k8s/consul-k8s/control-plane/main.go:21
runtime.main
/opt/hostedtoolcache/go/1.20.4/x64/src/runtime/proc.go:250
2023-06-07T15:59:25.641Z [INFO] consul-server-connection-manager: stopping
Stream closed EOF for gftx-fs/consul-connect-injector-79cdf676c4-mpd85 (sidecar-injector)`
connect-inject overrides
`connectInject:
enabled: true
replicas: 1
image: null
default: false
apiGateway:
manageExternalCRDs: true
managedGatewayClass:
nodeSelector: null
tolerations: null
serviceType: ClusterIP
copyAnnotations:
service: null
deployment:
defaultInstances: 1
maxInstances: 1
minInstances: 1
serviceAccount:
annotations: null
resources:
requests:
memory: "100Mi"
cpu: "100m"
limits:
memory: "100Mi"
cpu: "100m"`
The text was updated successfully, but these errors were encountered: