Hi all!
I'm traying to instantiate my eks (with fargate) cluster to deploy bitbucket autoscaler following this guide, but whene i'm on the stepo of deploy it with command:
kubectl apply -k values
seems that the only two pods runner-controller and runner-controller-cleaner finishes in CrashLoopBackOff with the following log:
INFO: Config file provided /opt/conf/config/runners_config.yaml.
INFO: File /opt/conf/job_template/job.yaml.template copied to /home/bitbucket/autoscaler/resources/job.yaml.template
✖ 1 validation error for RunnerData
groups -> 0 -> __root__
'latin-1' codec can't encode characters in position 4-6: ordinal not in range(256) (type=value_error.unicodeencode)
what it could be? Seems a bug in the container startup.
note: before i issue these command i followed all steps described in the guide, plus adding this annotations on the two pods yaml, to let k8s scheduler run those pods on the fargate nodes:
tolerations:
- key: "eks.amazonaws.com/compute-type"
operator: "Equal"
value: "fargate"
effect: "NoSchedule"
becouse without it seems that the pods remain in pending state.
