podman

Deploy with podman

In this scenario the service and associated components are deployed onto your local host in containers using Podman.

Requirements

Make sure you have podman version 3.3+ installed. If you must use an older version of podman, reference the previous documentation and procedure to avoid a podman bug.

Grab pod.yml and configmap.yml from this directory. No need to clone the whole repo.

Change IMAGE_SERVICE_BASE_URL and SERVICE_BASE_URL in configmap.yml to match the hostname or IP address of your host. For example if your IP address is 192.168.122.2, then the SERVICE_BASE_URL would be set to http://192.168.122.2:8090. Port 8090 is the assisted-service API that agents will connect to.

Optional Configuration

Other environment variables may be set in configmap.yml. For example, custom agent (AGENT_DOCKER_IMAGE), installer (INSTALLER_IMAGE) and controller (CONTROLLER_IMAGE) images can be defined.

Run it

podman play kube --configmap configmap.yml pod.yml

To preserve data about existing clusters between pod reconfigurations the pod-persistent.yml manifest could be use instead, which creates additional volumes for database and cluster's artifacts:

podman play kube --configmap configmap.yml pod-persistent.yml

If you only want to provision a single cluster at a time, which is a common use case, persistence is not necessary.

The UI will available at: http://<host-ip-address>:8080

Remove it

podman play kube --down pod.yml

OKD configuration

Assisted Service can install OKD clusters using a different set of parameters:

podman play kube --configmap okd_configmap.yml pod.yml

or

make deploy-onprem OKD=true

for developers

Configuration differences are:

• OS_IMAGES should point to Fedora CoreOS (see Fedora CoreOS Release artifacts)
• RELEASE_IMAGES lists available OKD versions (see OKD Releases)
• OKD_RPMS_IMAGE is additional image containing Kubelet/CRI-O RPMs (see example repo)