In this exercise, we’ll review creating a new image via automation to host a kubernetes application on small form factor hardware.
For a reminder on the application we’re deploying, review exercise 1.5.
Note
Kubernetes functionality will not work on devices that only have a wireless connection. If you have a physical device on WiFi, consult with your instructor for next steps.
We’re now going to deploy a Kubernetes-based application to our edge devices. To accomplish this, we’ll need to add a very small footprint Kubernetes build to our devices to enable the running of k8s-based applications.
A quick note: This is referred to in the upstream simply as MicroShift. The workshops are not yet updated to leverage the 4.12 official releases of the Red Hat Build of MicroShift, supported by the Red Hat Device Edge SKU. Because of this, some functionality may be incomplete.
In the interest of time, these steps have been completed for you and will be made available by the instructor. This image was composed using the infra.osbuild Ansible collection, which takes a common set of variables and completely automates interactions with Image Builder.
Specifically, this image was customized with the following variables:
- version: 4.0.0
type: edge-commit
repos:
- name: EPEL8
base_url: "https://dl.fedoraproject.org/pub/epel//Everything/x86_64/"
type: yum-baseurl
check_ssl: true
check_gpg: false
- name: microshift
base_url: https://download.copr.fedorainfracloud.org/results/@redhat-et/microshift-testing/epel-8-x86_64/
type: yum-baseurl
check_ssl: true
check_gpg: false
- name: microshift-deps
base_url: https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rpms/4.12-el8-beta/
type: yum-baseurl
check_ssl: true
check_gpg: false
packages:
- vim-enhanced
- git
- nano
- microshift
- NetworkManager-wifi
- ansible-core
Proceed to this exercise for next steps on how to get your device updated to the correct image version.
Navigation
Previous Exercise | Next Exercise |