Actions
Task #5404
closed
Story #5598: [Epic] Long-Term To-Do for pulp-operator
Container CI testing shouldn't install packages onto the pulp-api container
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
h1. !! Ticket moved to GitHub: "pulp/pulp-operator/261":https://github.com/pulp/pulp-operator/issues/261
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.
Actions
.