Openshift Auto Upi Versions Save

OpenShift Automated User-Provided Infrastructure

1.9

2 years ago
  • Use CoreOS stream metadata to determine CoreOS image version. User doesn't need to specify the CoreOS image version any longer.
  • Allow multiple roles for node (master, infra, worker). This enables single-node-cluster deployments where the single node plays the role of master and infra node at the same time.
  • Allow adding custom domain records to DNS. Use the additional_host_lines setting in dns_server.yml
  • Shut down boostrap host and wait for installation to complete
  • Allow nested-virtualization in Libvirt
  • Enable virtio random number generator in Libvirt
  • Add MTU customization example
  • Note that this openshift-auto-upi version only supports OpenShift >= 4.8. Use openshift-auto-upi version <= 1.8 for installing OpenShift < 4.8
  • Update software to the latest versions:
    • OCP 4.9.9

1.8

2 years ago
  • Allow users to specify arbitrary OpenShift version (see also issue #33)
  • Fixed deployment to vSphere. Issue caused by incorrect use of vmware_guest_network
  • Fixed failed boot on oVirt when using static IPs
  • When deleting oVirt virtual machine, delete the respective boot ISO used for static IPs as well
  • Install python3-ovirt-engine-sdk4 on RHEL8 and Fedora
  • Remove etcd-related DNS records that are not needed since OpenShift >= 4.4
  • Host of documentation updates
  • Updated software to the latest versions:
    • OCP 4.7.16

1.7

2 years ago
  • Fixed virtual machine creation on vSphere 7.0.2
  • Fixed deployment on oVirt 4.4. Thanks @arjanvanham !
  • Reimplemented vSphere static IPs using guestinfo variables (requires OCP version >= 4.6)
  • Added delete_vsphere.yml and delete_ovirt.yml playbooks for deleting all provisioned VMs on vSphere and oVirt
  • Added delete_install_config.yml playbook for scrubbing OpenShift installer configuration
  • Updated software to the latest versions:
    • OCP 4.7.13, CoreOS 4.7.7
    • OKD 4.7.0-0.okd-2021-06-04-191031, FCOS 33.20210117.3.2

1.6

3 years ago
  • Support for static IPs deployments to Libvirt PXE and bare metal target platforms.
  • User can customize ignition config files using filetranspiler and jsonpatch, see also Customizing Ignition Configs.
  • Support for deploying OKD - the community distribution of Kubernetes.
  • Fixed up and updated registry mirror to work with OCP 4.5.4.
  • Updated software to the latest versions:
    • OCP 4.5.4, CoreOS 4.5.2

1.5

3 years ago
  • Support for installing OpenShift using static IPs. Note that static IPs are only supported for vSphere and oVirt target platforms at this time.
  • Only wait for SSH connections on the newly created virtual machines. Previous versions of openshift-auto-upi were waiting for SSH connection on all existing virtual machines which was not correct. Previously provisioned OpenShift hosts can be down at the time openshift-auto-upi is executing.
  • Allow verifying server TLS certificates when connecting to vSphere and oVirt.
  • Updated software to the latest versions:
    • OCP 4.3.23, CoreOS 4.3.8
    • OCP 4.4.6, CoreOS 4.4.3

1.4

4 years ago
  • Much improved deployment to Libvirt, see the openshift_libvirt_fwcfg.yml playbook.
    • Creating virtual machines using a shared template disk image.
    • Ignition configuration is passed via QEMU firmware config which avoids the need for PXE booting.
    • The Libvirt installation using PXE boot is still available as a separate playbook openshift_libvirt_pxe.yml as it's useful for testing the PXE boot provisioning, and in contrast to the QEMU firmware config method, PXE boot works for the older RHEL7-based hypervisors.
  • vSphere deployment doesn't require HTTP server anymore. HTTP server was used to serve ignition files to OpenShift nodes. Ignition files are now sent to the vSphere APIs in their entirety and attached to OpenShift VMs as custom attributes. vSphere APIs don't specify the maxium allowed size for custom attributes, see also the respective WSDL definition I was able to upload up to 12 MB of data as custom attributes. The size of a typical ignition config file is less than 0.5 MB.
  • openshift-auto-upi is now going to power up only newly created virtual machines. Existing virtual machines which are part of the cluster are left intact.

1.2

4 years ago
  • Support oVirt (RHEV) as a target deployment platform
  • Prevent any accidental modification of the existing OpenShift hosts by skipping host creation tasks
  • Rename directory openshift-auto-upi-install to a more descriptive openshift-auto-upi-workspace

1.0

4 years ago

First release