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

Use an existing CoreOS template defined in the install-config.yaml during installation

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Minor Minor
    • openshift-4.14
    • None
    • Installer
    • None
    • False
    • False
    • Undefined

      Proposed title of this feature request

      CoreOS template definition in the install-config.yaml

      What is the nature and description of the request?
      My customer would like to be able to do the following:

      We would like to be able to point to an existing CoreOS template in the install-config.yaml during installation, and skip the current method of the installer to upload the template each time you install a cluster.

      I think this is a good suggestion, although we would need to be clear any management of templates is the customers issue, but to allow in the install-config.yaml an option to point at a template would be good.

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

      The reason for this is a multitude:

      • Remote work uploading a new template via VPN is a hassle
      • with multiple cluster having the same template multiple times is a waste.
      • save time during installation testing
      • easier management of templates at a central place for vsphere management

      4. List any affected packages or components.

            racedoro@redhat.com Ramon Acedo
            rhn-support-andbartl Andy Bartlett
            Votes:
            2 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: