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

Get cluster health before an update #7528

Merged
merged 5 commits into from
Dec 5, 2022
Merged

Get cluster health before an update #7528

merged 5 commits into from
Dec 5, 2022

Commits on Dec 1, 2022

  1. Get cluster health before an update 

    As per redpanda-data#3023 the cluster should
be healthy before starting put node in maintanance mode and after POD is
restarted.
    Rafal Korepta committed Dec 1, 2022
    Configuration menu
    Copy the full SHA
    e0491d1 View commit details
    Browse the repository at this point in the history

  2. k8s: Move admin API mock to shared package 

    In the statefulset unit test the admin API needs to be mocked as cluster
health should be available.
    Rafal Korepta committed Dec 1, 2022
    Configuration menu
    Copy the full SHA
    00acf24 View commit details
    Browse the repository at this point in the history

  3. k8s: Create negative test for upgrade procedure 

    When cluster is unhealthy the upgrade/restarting procedure should not be
executed.
    Rafal Korepta committed Dec 1, 2022
    Configuration menu
    Copy the full SHA
    bb10e0a View commit details
    Browse the repository at this point in the history

  4. k8s: Adjust upgrade end to end tests 

    Before 22.X the cluster health overview is not available. All tests could not
upgrade from 21.X as operator could validate the health status.
    Rafal Korepta committed Dec 1, 2022
    Configuration menu
    Copy the full SHA
    c93d967 View commit details
    Browse the repository at this point in the history

  5. k8s: Remove require client authorization Admin API 

    In the centralized configuration e2e test the cluster health can not be
retrieved if required client authorization is removed from Admin API. Nodes
that are running with mTLS configuration does not respond to operator get
health overview. If first out of N brokers is restarted and stops serving
Admin API with mTLS configuration, then rpk adminAPI implementation sends
http request to all in sequence get health overview. The problem is with
http client and TLS configuration as one out of N doesn not need client
certificate.
    Rafal Korepta committed Dec 1, 2022
    Configuration menu
    Copy the full SHA
    2d775e6 View commit details
    Browse the repository at this point in the history