Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-1678

Refactor nodepool controller config generation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • Hypershift Sprint 258, Hypershift Sprint 259, Hypershift Sprint 260
    • 0
    • 0
    • 0

      As as dev I want to easily add and understand which input results in triggering a nodepool upgrade.

      There's many scattered things that triggers nodepool rolling upgrade on change.
      For code sustainability it'd be good to try to have a common abstraction that discovers all of them based on an input and return the authoritative hash for any targeted config version in time.
      Related https://github.com/openshift/hypershift/pull/4057
      https://github.com/openshift/hypershift/pull/3969#discussion_r1587198191

              agarcial@redhat.com Alberto Garcia Lamela
              agarcial@redhat.com Alberto Garcia Lamela
              He Liu He Liu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: