This repository contains UBI based versions of container images used in the Sumo Logic Kubernetes Collection Helm Chart. These UBI based versions of container images are used in the Sumo Logic Kubernetes Collection Helm Operator and all of them need to pass Red Hat Certification, for details please see Red Hat Software Certification Workflow Guide.
We can certify two types of images from this repo,
- Components built from this repo.
- Components built from a different repo. Ex, sumologic-otel-collector, tailing-sidecar etc.
To build and certify UBI based container images please open actions:
- To build components from this repo, use check, build and push worflows to do the respective operations on sumologic public AWS ECR repo. Once new components are built, use certify operation to push to openshift repository.
- check, build and push workflows aren't applicable for components from other repositories like sumologic-otel-collector, we just use this repo to certify them.
- Goto respective components public ECR repository and choose the version to certify. Ex. repository: sumologic-otel-collector , version: 0.130.1-sumo-0
- Enable force push operation when certifying these components.
Important Note: While using both the above methods, always make sure to use a new version which is not already present in redhat connect repository for the component which you're trying to update unless you are specifically trying to update an existing component.
Container certification (Legacy method, preserving since we have the workflows and need to understand what they do)
To build and certify UBI based container images please open actions:
- run Manually check all container images workflow, analyze logs and make steps according to log messages.
- run Manually certify all container images workflow, analyze logs and make steps according to log messages.
To get list of certified images make following steps:
-
login to Red Hat Container registry, e.g.:
docker login registry.connect.redhat.com -u <USER_NAME>
-
run:
make verify
If some of images are not pushed to Red Hat Container registry, please verify the status in Red Hat Partner Connect.
All the scripts used for container certification can be found in scripts directory, for details please see documentation.
Prepared development environment with all necessary components is available as virtual machine.
Please install the following:
brew install --cask virtualbox
brew install --cask vagrantYou'll need to use QEMU instead of VirtualBox to use Vagrant on ARM. The following instructions will assume an M1 Mac as the host:
- Install QEMU:
brew install qemu - Install the QEMU vagrant provider:
vagrant plugin install vagrant-qemu - Provision the VM with the provider:
vagrant up --provider=qemu
You can set up the Vagrant environment with just one command:
vagrant upAfter successful installation you can ssh to the virtual machine with:
vagrant sshTo remove virtual machine use:
vagrant destroy