the pod of submariner-engine always Back-off

[RocMe]

when I exec "helm install submariner-latest/submariner
--name submariner
--namespace submariner
--set ipsec.psk="${SUBMARINER_PSK}"
--set broker.server="${SUBMARINER_BROKER_URL}"
--set broker.token="${SUBMARINER_BROKER_TOKEN}"
--set broker.namespace="${SUBMARINER_BROKER_NS}"
--set broker.ca="${SUBMARINER_BROKER_CA}"

--set submariner.clusterId="<CLUSTER_ID>"
--set submariner.clusterCidr="<CLUSTER_CIDR>"
--set submariner.serviceCidr="<SERVICE_CIDR>"
--set submariner.natEnabled="<NAT_ENABLED>"
the submariner-engine pod status:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
submariner-engine-token-llv7j:
Type: Secret (a volume populated by a Secret)
SecretName: submariner-engine-token-llv7j
Optional: false
QoS Class: BestEffort
Node-Selectors: submariner.io/gateway=true
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message

---

Normal Scheduled 85s default-scheduler Successfully assigned submariner/submariner-585556659b-txbb4 to instance-qynqwmj9-1
Normal Pulling 34s (x4 over 85s) kubelet, instance-qynqwmj9-1 pulling image "rancher/submariner:v0.0.1"
Normal Pulled 33s (x4 over 81s) kubelet, instance-qynqwmj9-1 Successfully pulled image "rancher/submariner:v0.0.1"
Normal Created 33s (x4 over 81s) kubelet, instance-qynqwmj9-1 Created container
Normal Started 33s (x4 over 81s) kubelet, instance-qynqwmj9-1 Started container
Warning BackOff 8s (x7 over 78s) kubelet, instance-qynqwmj9-1 Back-off restarting failed container
I want to know how to fix it .Thanks.

[Oats87]

Did you just blindly run that helm install command or did you populate the fields?

[RocMe]

Did you just blindly run that helm install command or did you populate the fields?

sure . I got values fields from broker cluster and set them. example :
I exec on broker cluster
echo $SUBMARINER_BROKER_NS
submariner-k8s-broker

then I do west cluster
SUBMARINER_BROKER_NS="submariner-k8s-broker"
and so on

[RocMe]

Did you just blindly run that helm install command or did you populate the fields?

something I have to mention . I try to build submariner based on k3s not k8s .

[RocMe]

I see the log of the error log
envconfig.Process: assigning SUBMARINER_NATENABLED to NatEnabled: converting '<NAT_ENABLED>' to type bool. details: strconv.ParseBool: parsing "<NAT_ENABLED>": invalid syntax

I try to set NAT_ENABLED in 3 ways:
NAT_ENABLED=false
NAT_ENABLED="false"
NAT_ENABLED=0

I got the same log based on the k3s .Could you help me , thank you.

[mangelajo]

Closing old issue with no activity for 6+ months. Please re-open if you still need help with this. Hopefully subctl is of help here.