Uploaded image for project: 'OpenShift Hive'
  1. OpenShift Hive
  2. HIVE-2896

[F|S]FDC for installer manifests

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None

      Today it is very difficult to introspect the manifests generated by openshift-install create manifests during the provisioning process, either before or after we have modified them via specific code paths (e.g. additional security groups) or user-supplied patches.

      This spike is to brainstorm ways in which we could get access to these artifacts for debugging.

      A couple of quick thoughts off the top:

      • A flag asking installmanager to pause at various points, allowing us to enter a debug session on the pod and inspect the files in the file system.
      • A flag asking installmanager to offload those files somewhere (S3, one or more Secrets, the ClusterProvision, ...) at various points.

      The flag could take the form of an annoation, an API field, etc.

      The product of this spike should be a mostly-fleshed-out design concept that picks a specific way to do this thing. Or, if we decide it's not feasible, a justification for not pursuing it.

              Unassigned Unassigned
              efried.openshift Eric Fried
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: