Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-665

Enable adding a BYOH instance from outside the cluster's platform

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • 4.0.0
    • None
    • wmco
    • None
    • False
    • False
    • undefined

      Description

      Currently all instances configured by WMCO will have the same kubelet flags used, partially sourced from the worker ignition file. The `cloud` flag is based upon the clusters `platform`, and directly affects how kubelet functions. In the case where a user wants to join an instance provisioned not via the cloud provider, the current result is that the kubelet will attempt to use the cloud provider to resolve information about the instance. This will cause issues, as the cloud provider will have no knowledge about the instance. Instead, the cloud flag should not be set, making kubelet determine information about the instance through its own methods.

      This is not an issue if the cluster's platform is `none`.

      Engineering Details

      There needs to be a way to identify which instances should have the cloud flag set to none. One way to do this is to expand the windows-instances ConfigMap API to include a field such as "no-cloud", and instances where that field is true should have the cloud flag set appropriately.

      Acceptance Criteria

      • A Windows BYOH instance not created through the cluster's cloud provider can be joined to the cluster.

              Unassigned Unassigned
              rh-ee-ssoto Sebastian Soto
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: