Project

Profile

Help

Task #5404

Story #5598: [Epic] Long-Term To-Do for pulp-operator

Container CI testing shouldn't install packages onto the pulp-api container

Added by mdepaulo@redhat.com about 1 year ago. Updated about 2 months ago.

Status:
NEW
Priority:
Normal
Category:
Operator
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

Currently in order to do CI testing, plugin-template installs RPM and python packages into the pulp-api container.

This has 3 problems:
1. It is brittle. If pulp-api is restarted, they are lost.
2. It means the container image is being modified; which could possibly invalidate tests.
3. It is probably not the correct design pattern.

This task is to reach the correct design pattern, and implement it.
A possible alternative pattern is running tests from a separate sidecar container in the same pod.

History

#1 Updated by mdepaulo@redhat.com about 1 year ago

  • Parent task set to #5598

#2 Updated by fao89 12 months ago

  • Tags CI/CD added

#3 Updated by bmbouter about 2 months ago

  • Category set to Operator

Please register to edit this issue

Also available in: Atom PDF