k8s retry-join exclude itself because of non-readiness

[jacobsin]

Describe the bug
dkron k8s retry-join seems to exclude itself because readiness probe return non 200

To Reproduce
Steps to reproduce the behavior:

1. Add config retry-join: ['provider=k8s']
2. Create statefulset with 1 node
3. See error

discover.go:178 [DEBUG] discover: Using provider \"k8s\"
k8s_discover.go:150 [DEBUG] discover-k8s: ignoring pod \"dkron-node-0\", not ready state

Expected behavior
Perhaps the starting dkron node should know itself starting and accept itself joining the cluster?

Specifications

• OS: linux
• Version 3.2.3

[vcastellm]

Can you take a look to this dkron-io/dkron-helm#3, and check if it helps?

[vcastellm]

Should be fixed by #1446