Comment 1 for bug 2030901

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to vault-armada-app (master)

Reviewed: https://review.opendev.org/c/starlingx/vault-armada-app/+/891091
Committed: https://opendev.org/starlingx/vault-armada-app/commit/f7a37e6ad91b7a0efa79c9cb9783af343344ad33
Submitter: "Zuul (22348)"
Branch: master

commit f7a37e6ad91b7a0efa79c9cb9783af343344ad33
Author: Tae Park <email address hidden>
Date: Thu Aug 10 14:16:40 2023 -0400

    Removing default injector anti-affinity rules

    Adding a null override over default anti-affinity rules for vault injectors. The default rule only allow one vault injector pod at a time. This is a problem because helm-override and application apply will try to schedule a new pod first before completely removing the old pod.
    This change lets a new vault agent injector pod to be scheduled without issue.

    TEST PLAN:
     - Test for AIO-SX
     - Update helm-override so that vault-injector has a different image tag than default
     - apply the new helm-override
     - There should be no FailedScheduling error in the vault pods
     - Sanity test for both AIO-SX and AIO-DX + 1 worker

    Closes-bug: 2030901

    Change-Id: I9814f502558ab1cbecad48cf37341639c964258f
    Signed-off-by: Tae Park <email address hidden>