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

HyperShift In-Place Resource Propagation

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Hosted Control Planes
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      HyperShift In-Place Resource Propagation for Secrets and Configuration Changes
       

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

      This RFE requests the implementation of in-place resource propagation capabilities in HyperShift to automatically detect and apply changes to critical resources (such as pull secrets, trusted bundles, and registry configurations)
       
      Proposed Solution:

      • Implement intelligent change detection for specific resource types that can be safely updated in-place
      • Develop propagation mechanisms that automatically apply changes to all expected areas and components without node replacement
      • Provide selective rollout behavior where only resources requiring full replacement trigger nodepool rollouts
      • Ensure automatic synchronization across all HyperShift components when configuration changes occur
         

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

      Operational Efficiency:

      • ARO HCP requires the ability to rotate security credentials (pull secrets, certificates) without causing service disruption
      • Current rollout behavior creates unnecessary operational overhead and maintenance windows
      • In-place updates significantly reduce the time required for credential rotation operations
         

      Business Continuity:

      • Minimizing pod churn and service disruption is critical for production workloads
      • Customers need to maintain high availability while performing routine security maintenance
      • Reducing rollout frequency improves overall cluster stability and predictability
         

      Security Compliance:

      • Regular credential rotation is a security best practice and regulatory requirement
      • Current implementation creates friction that may discourage proper security hygiene
      • Seamless credential rotation enables automated security workflows
         

      4. List any affected packages or components.

      Primary Components:

      • HyperShift Operator - Core orchestration logic for change detection and propagation
      • Control Plane Operator - Management of HC input processing and validation

              racedoro@redhat.com Ramon Acedo
              dffrench@redhat.com David Ffrench
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None