Skip to content

Kubernetes service discovery breaking change in version 29.0.0 #17529

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

Closed
m17kea wants to merge 1 commit into from
Closed

Kubernetes service discovery breaking change in version 29.0.0 #17529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/release-info/upgrade-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,34 @@ Removed the `auto` search strategy from the native search query. Setting `search

[#15550](https://github.com/apache/druid/pull/15550)

### Incompatible changes

#### Changes to date format in kubernetes service discovery

Druid 29.0.0 includes a breaking change for those using kubernetes service discovery. The date format used in the config maps used for leader election of coordinators and overlords has changed.
Copy link
Contributor

@kfaraz kfaraz Mar 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please describe the error a little more or maybe include an example of the encountered error message.


If you're upgrading from any version prior to 29.0.0 manual intervention is required. The steps to fix are as follows:

kubectl get cm -n <druid namespace>

you should see 2 config maps of the form:

<cluster-identifier>-leaderelection-coordinator
<cluster-identifier>-leaderelection-overlord

verify the date from your error message appears in the annotations:

kubectl describe cm <cluster-identifier>-leaderelection-coordinator -n <druid namespace>
kubectl describe cm <cluster-identifier>-leaderelection-overlord -n <druid namespace>

remove these by:

kubectl delete cm <cluster-identifier>-leaderelection-coordinator -n <druid namespace>
kubectl delete cm <cluster-identifier>-leaderelection-overlord -n <druid namespace>

These will be recreated by the services which will then successfully start.


## 28.0.0

### Upgrade notes
Expand Down