Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4655

A method to trigger pod restart after the secret/configmap is updated

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • openshift-4.11
    • Auth
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      1. Proposed title of this feature request

      A method to trigger pod restart after the secret/configmap is updated

      2. What is the nature and description of the request?

      Customer is running Ansible Automation Platform 2.3 deployed via AAP operator 2.3.0+0.1692726125 and using an external PostgresSQL. 
      The secret of the PostgresSQL gets rotated regularly. Customer also have External Secret Operator (upstream project) running on the clusters that constantly checks and pull in the latest password and update the secret in OpenShift

      When the PostgresSQL secret is updated and correctly reflected in OpenShift, AAP doesn't restart its pods. Reason Customer opened the case and later agreed with opening this RFE.

      3. Why does the customer need this? (List the business requirements here)

      The purpose of this RFE is automation of repetitive tasks (restarting `pods` after a `secret` is changed).

      4. List any affected packages or components.

      Customer currently uses RHOCP 4.11. Other components' versions are listed under question #2.

            gausingh@redhat.com Gaurav Singh
            rhn-support-rdeolive Rafael de Oliveira Rosa
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: