Skip to content

Conversation

@naemono
Copy link
Contributor

@naemono naemono commented Oct 22, 2025

Fixes #8429

What is changing?

This ensure that the master StatefulSets are always upgraded last when doing a version upgrade of Elasticsearch.

Validation

  1. Manual testing
  2. Unit test for behavior
  3. e2e test validating behavior

@prodsecmachine
Copy link
Collaborator

prodsecmachine commented Oct 22, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@botelastic botelastic bot added the triage label Oct 22, 2025
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
@naemono
Copy link
Contributor Author

naemono commented Oct 29, 2025

buildkite test this -f p=kind,t=TestNonMasterFirstUpgradeComplexTopology -m s=9.1.2

Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
…/cloud-on-k8s into fix-sts-upgrade-issue-recreation
@naemono
Copy link
Contributor Author

naemono commented Oct 29, 2025

buildkite test this -f p=kind,t=TestHandleUpscaleAndSpecChanges_VersionUpgradeDataFirstFlow -m s=9.1.2

Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
@naemono naemono changed the title WIP: Upgrade masters last when upgrading ES clusters Upgrade masters last when upgrading ES clusters Oct 29, 2025
@naemono naemono marked this pull request as ready for review October 29, 2025 23:21
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR implements a non-master-first upgrade strategy for Elasticsearch clusters. The key change ensures that during version upgrades, non-master nodes (data, ingest, coordinating nodes) are upgraded before master nodes, which helps maintain cluster stability during upgrades.

  • Adds logic to separate master and non-master StatefulSets during version upgrades
  • Implements upgrade order validation to ensure non-master nodes complete their upgrades first
  • Adds comprehensive unit and e2e tests to verify the upgrade flow

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
pkg/controller/elasticsearch/driver/upgrade.go Adds check to identify new clusters vs upgrades by checking if status version is empty
pkg/controller/elasticsearch/driver/upscale.go Implements non-master-first upgrade logic with resource separation and upgrade status checking
pkg/controller/elasticsearch/driver/upscale_test.go Adds comprehensive unit test for version upgrade flow and minor formatting fixes
test/e2e/es/non_master_first_upgrade_test.go Adds e2e test that validates non-master-first upgrade behavior with a watcher

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Signed-off-by: Michael Montgomery <[email protected]>
@barkbay barkbay added the >bug Something isn't working label Nov 3, 2025
@botelastic botelastic bot removed the triage label Nov 3, 2025
@barkbay barkbay dismissed their stale review November 17, 2025 15:22

Dismiss my review to avoid blocking the merge of this PR. I'll try to run some new tests later.

Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
@naemono naemono force-pushed the fix-sts-upgrade-issue-recreation branch from d82eb76 to 518d69d Compare November 17, 2025 16:53
@naemono naemono requested a review from barkbay November 18, 2025 00:43
@barkbay
Copy link
Contributor

barkbay commented Nov 26, 2025

I'll take another look today, sorry for the lag.

pendingNonMasterSTS = append(pendingNonMasterSTS, actualStatefulSet)
continue
}

Copy link
Contributor

Choose a reason for hiding this comment

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

We should not rely on the status until the sts controller has observed the new generation.

Suggested change
if actualStatefulSet.Status.ObservedGeneration < actualStatefulSet.Generation {
// The StatefulSet controller has not yet observed the latest generation.
pendingNonMasterSTS = append(pendingNonMasterSTS, actualStatefulSet)
continue
}

Copy link
Contributor

Choose a reason for hiding this comment

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

or:

  • use actualStatefulSets.PendingReconciliation() before that loop
  • create a common function to reuse the logic in
    func (d *defaultDriver) expectationsSatisfied(ctx context.Context) (bool, string, error) {
    log := ulog.FromContext(ctx)
    // make sure the cache is up-to-date
    expectationsOK, reason, err := d.Expectations.Satisfied()
    if err != nil {
    return false, "", err
    }
    if !expectationsOK {
    log.V(1).Info("Cache expectations are not satisfied yet, re-queueing", "namespace", d.ES.Namespace, "es_name", d.ES.Name, "reason", reason)
    return false, reason, nil
    }
    actualStatefulSets, err := sset.RetrieveActualStatefulSets(d.Client, k8s.ExtractNamespacedName(&d.ES))
    if err != nil {
    return false, "", err
    }
    // make sure StatefulSet statuses have been reconciled by the StatefulSet controller
    pendingStatefulSetReconciliation := actualStatefulSets.PendingReconciliation()
    if len(pendingStatefulSetReconciliation) > 0 {
    log.V(1).Info("StatefulSets observedGeneration is not reconciled yet, re-queueing", "namespace", d.ES.Namespace, "es_name", d.ES.Name)
    return false, fmt.Sprintf("observedGeneration is not reconciled yet for StatefulSets %s", strings.Join(pendingStatefulSetReconciliation.Names().AsSlice(), ",")), nil
    }
    // make sure pods have been reconciled by the StatefulSet controller
    return actualStatefulSets.PodReconciliationDone(ctx, d.Client)
    }

@naemono naemono requested review from barkbay and pebrc December 1, 2025 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug Something isn't working v3.3.0 (next)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] ECK should only Update Elasticsearch StatefulSet version when attempting to upgrade the StatefulSet Pods

4 participants