...
The resource requirements for deployment depend on the specific blueprint and deployment target. Please see:
...
The baremetal UPI install can be optionally automated when using knictl (see below). When attempting a manual baremetal UPI install, however, please be sure to read: https://docs.openshift.com/container-platform/4.1/installing/installing_bare_metal/installing-bare-metal.html
Pre-Requisites for Deploying to Google Cloud Platform
For deploying a KNI blueprint to GCP, you need to:
- enable service APIs
- setup DNS
- ensure sufficient quota
- create a installer service account
Please, see the upstream documentation for details. As mentioned in the KNI installer repo, the service account JSON file should be located inside $HOME/.gcp with the name osServiceAccount.json.
Pre-Requisites for Deploying to Libvirt
For deploying a KNI blueprint to VMs on KVM/libvirt, you need to
...
Please see the upstream documentation for details.
Create site for AWS, GCP and libvirt
In order to deploy a blueprint, you need to create a repository with a site. The site configuration is based in kustomize, and needs to use our blueprints as base, referencing that properly. Sample sites for deploying on libvirt, AWS and baremetal can be seen on: https://github.com/akraino-edge-stack/kni-blueprint-pae/tree/master/sites.
Site needs to have this structure:
...
Follow same structure as 01_cluster_mods, but in this case is for adding additional workloads after cluster deployment. They also need to have a kustomization.yaml file that references the file of the same level for the blueprint, and can include additional resources and patches.
How to deploy on AWS, GCP and libvirt
The whole deployment workflow is based on knictl CLI tool that this repository is providing.
...
This file is not shown on the site structure as it contains private content. This file should be present with given name in 00_install-config. It needs to have following structure:
...