Failed to start consul by minikube by the tutorial

hashicorp / learn-consul-kubernetes

Mozilla Public License 2.0

32 stars 36 forks source link

Failed to start consul by minikube by the tutorial #60

Open joejiang-wish opened 2 years ago

joejiang-wish commented 2 years ago

Env

machine: Macos arch: arm64 system version: 12.1

Description

Failed start consul by minikube by the tutorial at here

The error in restarting pod consul-connect-injector-xx is flag provided but not defined: -default-consul-sidecar-memory-limit.

How to fix

Update the imageK8S key in deploy/config.yaml to from hashicorp/consul-k8s-control-plane:0.39.0 to hashicorp/consul-k8s-control-plane:0.42.0.

krastin commented 2 years ago

Hi @joejiang-wish! Thank you for reporting this issue - the repository has since been updated: https://github.com/hashicorp/learn-consul-kubernetes/blob/8d5b693a09500bdf252aac8a527616700637c954/service-mesh/deploy/config.yaml#L6 However I do not have an ARM Mac to verify this has fixed the issue. Could you confirm everything works well now?

BrianMMcClain commented 2 years ago

Howdy! Not sure if this is the right place to chime in or if I should open a new issue, I ran into something similar running on Minikube where the consul-connect-injector pods would report a status of CrashLoopBackOff:

k logs -n consul consul-connect-injector-84d5645586-64kfm

flag provided but not defined: -enable-cni
[...]

Similar to how this error was fixed, I updated config.yaml to the latest version on Docker Hub to read:

imageK8S: hashicorp/consul-k8s-control-plane:0.48.0

This was on an Intel Mac running macOS 12.3.1. Hope this is helpful, thanks! 😄