Task #5061
closed
Task #5069: Build pulp 3 containers
Develop a script to launch pulp containers with k3s, for CI
100%
Description
In order to enable CI testing Pulp in containers, we need a script to launch them (and handle the shared variables and all between them) with docker/podman, rather than a K8s operator.
Updated by ipanova@redhat.com over 5 years ago
- Status changed from NEW to ASSIGNED
Updated by mdepaulo@redhat.com over 5 years ago
k3s (lightweight Kubernetes) with our operator might be a better alternative for the Travis CI needs:
https://k3s.io/
Updated by dkliban@redhat.com over 5 years ago
- Sprint changed from Sprint 55 to Sprint 56
Updated by mdepaulo@redhat.com over 5 years ago
- % Done changed from 0 to 70
I decided to use k3s instead.
I am mostly done. I've had to resolve lots of medium-size issues, like registry.centos.org not working with k3s, k3s not having a storage plugin, and establishing proper checks for the containers being deployed successfully.
https://github.com/mikedep333/pulp-operator/tree/k3s-travis
I've been talking a lot with dkilban and mmello. mmello has been wanting k3s compatibility.
Added by Mike DePaulo over 5 years ago
Updated by mdepaulo@redhat.com over 5 years ago
The reasoning for using k3s are:
1. It improves the CI for pulp-operator itself.
2. It is less work to adapt pulp-operator for k3s than to write & maintain new a big script that needs features like configmaps.
3. Users like mmello want k3s support anyway.
4. I did not know about k3s at the time I wrote this issue.
Updated by mdepaulo@redhat.com over 5 years ago
- Status changed from ASSIGNED to POST
Updated by mdepaulo@redhat.com over 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 90 to 100
https://github.com/pulp/pulp-operator/pull/7 was merged
Updated by mdepaulo@redhat.com over 5 years ago
- Status changed from MODIFIED to 5
Updated by mdepaulo@redhat.com over 5 years ago
- Subject changed from Develop a script to launch 4 pulp containers in just Docker/Podman to Develop a script to launch pulp containers with k3s, for CI
Updated by mdepaulo@redhat.com over 5 years ago
- Status changed from 5 to CLOSED - COMPLETE
.
Have Travis use k3s to test the containers.
Test basic Pulp functionality, including writing to disk Using pulp_file's sync tests.
Also, don't set CONTENT_HOST in the pulp-server ConfigMap. If set incorrectly, it causes pulp_file test scripts to fail. We haven't implemented querying it via the K8s APIs, or having users specify it yet.
Note that the RequestsDependencyWarning messages from httpie are annoying output, but pip3 is not on Ubuntu on Travis. It appears that Travis relies on the virtual env for Python3
fixes #5061 https://pulp.plan.io/issues/5061