Project

Profile

Help

Task #5061

Task #5069: Build pulp 3 containers

Develop a script to launch pulp containers with k3s, for CI

Added by mdepaulo@redhat.com almost 2 years ago. Updated almost 2 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 56
Quarter:

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.

Associated revisions

Revision bcbf5280 View on GitHub
Added by Mike DePaulo almost 2 years ago

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

History

#1 Updated by daviddavis almost 2 years ago

  • Parent task changed from #5004 to #5069

#2 Updated by ipanova@redhat.com almost 2 years ago

  • Status changed from NEW to ASSIGNED

#3 Updated by mdepaulo@redhat.com almost 2 years ago

k3s (lightweight Kubernetes) with our operator might be a better alternative for the Travis CI needs:
https://k3s.io/

#4 Updated by dkliban@redhat.com almost 2 years ago

  • Sprint changed from Sprint 55 to Sprint 56

#5 Updated by mdepaulo@redhat.com almost 2 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.

#6 Updated by mdepaulo@redhat.com almost 2 years ago

  • % Done changed from 70 to 90

#7 Updated by mdepaulo@redhat.com almost 2 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.

#8 Updated by mdepaulo@redhat.com almost 2 years ago

  • Status changed from ASSIGNED to POST

#9 Updated by mdepaulo@redhat.com almost 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 90 to 100

#10 Updated by mdepaulo@redhat.com almost 2 years ago

  • Status changed from MODIFIED to 5

#11 Updated by mdepaulo@redhat.com almost 2 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

#12 Updated by mdepaulo@redhat.com almost 2 years ago

  • Status changed from 5 to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF