-
Notifications
You must be signed in to change notification settings - Fork 22
Closed
Milestone
Description
The first step with making a Kubernetes deployment is to look into the kernelci-pipeline services which come with a docker-compose setup. These could be deployed in MiniKube while kernelci-api is running in a standard docker-compose deployment on the host. That way, a generic Kubernetes deployment solution for the pipeline services can be created in a fully self-contained way before deploying it again in a real Cloud (e.g. Azure) as a follow-up task.
- Local
kernelci-apiinstance set up and running with standarddocker-composedeployment - Running
kci api helloon the host returns the "KernelCI API" message from the local instance - MiniKube set up locally on the same host
- Pipeline services deployed in MiniKube so they can communicate with the local API instance
Note: thenotifierservice is the easiest one to bring up so it can be done first to get started
Note: the LAVA handler and KCIDB bridge defined in separate docker-compose files are out of scope for this issue - Configuration for automatically deploying all the pipeline services in Kubernetes tested with MiniKube
- Configuration (Terraform?) added to the
kernelci-pipelinerepository
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done