I’m trying to execute a simple kubernetes pipeline but when my pipeline failed immediately because kubernetes trying to spawn a pod to execute all my steps but this pod is immediately killed by kubernetes.
When I check the events I have the following weird outputs:
Normal Started 6s kubelet, ip-10-64-7-249.eu-central-1.compute.internal Started container Normal Created 5s (x2 over 10s) kubelet, ip-10-64-7-249.eu-central-1.compute.internal Created container Normal Killing 5s kubelet, ip-10-64-7-249.eu-central-1.compute.internal Killing container with id docker://drone-m5b4sok6jlj24kojgbfb:Container spec hash changed (3761618974 vs 538082423).. Container will be killed and recreated.
You can find my pipeline definition here:
--- kind: pipeline type: kubernetes name: test-first-pipeline steps: - name: example image: busybox commands: - echo "hello world" - echo "it's working"
And my pipeline failed immediately at the built-in
clone step. So my step
example is never executed.
Does drone patch something on the pod which cause this inconsistency ?
Please can someone help me with that issue ?