Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2016

CPMS: Investigate a way to surface the desired vs current ProviderSpec diff

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • 5
    • False
    • None
    • False
    • CLOUD Sprint 237, CLOUD Sprint 238

      User Story

      As a user I want to see what differs between the Machine's (current) ProviderSpec and the Control Plane Machine Set (desired) ProviderSpec so that I can understand why the CPMSO is replacing my control plane machine.

      Background

      Work spawn out of discussions in https://redhat-internal.slack.com/archives/CCX9DB894/p1678820665803259 and https://redhat-internal.slack.com/archives/C04UB95G802 

      Believe we are already logging this, would be good to emit either an event or the diff into the status, whoever takes this card should investigate the best way of surfacing this.

      Outcome:

      • Decision on event/status/both
      • If status, API design scoped out
      • Cards written for implementation

      Steps

      • PR
      • update tests

      Stakeholders

      • <Who is interested in this/where did they request this>

      Definition of Done

      • <Add items that need to be completed for this card>
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

            ddonati@redhat.com Damiano Donati
            ddonati@redhat.com Damiano Donati
            Huali Liu Huali Liu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: