Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1947

RHBoK (Kueue) - operator disconnected support

XMLWordPrintable

    • Product / Portfolio Work
    • OCPSTRAT-1692AI Workloads for OpenShift
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • S
    • None
    • None

      Feature Overview (aka. Goal Summary)  

      The Red Hat Build of Kueue (Kueue) will need to support being used in disconnected mode. While this is not possible in the earlier release due to cert manager dependancies but it should be addressed as soon as possible

      Goals (aka. expected user outcomes)

      RHBoK is supported in disconnected environments

      Requirements (aka. Acceptance Criteria):

      RHBoK is supported in disconnected environments

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both Both
      Classic (standalone cluster) Yes
      Hosted control planes Yes
      Multi node, Compact (three node), or Single node (SNO), or all All
      Connected / Restricted Network Both
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) x86_x64 initially
      Operator compatibility Yes
      Backport needed (list applicable versions) No
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) No
      Other (please specify) n/a

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

      <your text here>

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

      <your text here>

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

      <your text here>

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

      <your text here>

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      <your text here>

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      <your text here>

              rh-ee-kehannon Kevin Hannon
              scuppett@redhat.com Stephen Cuppett
              None
              Derek Carr, Kevin Hannon
              Mrunal Patel Mrunal Patel
              Kevin Hannon Kevin Hannon
              Aruna Naik Aruna Naik
              Matthew Werner Matthew Werner
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: