Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

k8s retry-join exclude itself because of non-readiness #1323

Open
jacobsin opened this issue May 3, 2023 · 2 comments
Open

k8s retry-join exclude itself because of non-readiness #1323

jacobsin opened this issue May 3, 2023 · 2 comments

Comments

@jacobsin
Copy link

jacobsin commented May 3, 2023 •
edited
Loading

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
Copy link
Member

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

@vcastellm
Copy link
Member

Should be fixed by #1446

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vcastellm @jacobsin