Project

Profile

Help

Story #5138

Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io

In pulp-operator, the pulp_content_host should be set to the actual accessible service URL

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

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

In pulp-operator, the $CONTENT_HOST / pulp_content_host to the actual accessible service URL that Kubernetes provides for clients to use.

We should query the K8s API for it.

Associated revisions

Revision 20e2315b View on GitHub
Added by Mike DePaulo about 2 months ago

Use containers for Travis CI

Fixes: #5004
migrate travis plugin-template to installing pulp in containers
https://pulp.plan.io/issues/5004

re: #5069
https://pulp.plan.io/issues/5069
Create pulpcore and pulp_file container images automatically via CI

Implementation includes:

Disabling codecov for the time being.

Only test on Python 3.7 for now, because Fedora 30 has only secondary
support for Python 3.6, and it would require multiple changes to test
against.

Fix using required PRs for pulp-smash.

Use pulp-smash master branch by default rather than stable release.

Use docker as provided by Travis (rather than k3s containerd).

Generate pulpcore/containers/var/vars.yaml, and build the container
image with the plugin & pulp-certguard.

Clone pulp-operator for its scripts to deploy k3s & the operator-
managed containers, and run those deployment scripts.

Generate a pulp-operator custom-reource with the settings needed for
testing.
(It must be generated because it points to the image name like
"pulp_rpm" rather than "pulp".)

Use `sudo kubectl exec` as a method for running commands in the
pulp-api container, $CMD_PREFIX .

Use $CMD_PREFIX to run the unit tests.

Install packages needed only for testing in the pulp-api container
as it runs.

script.sh: Wait for the content app to become online.

Move as much of the show_logs_and_return_non-zero logic to travis.yml
after_failure

Make func_test_script.sh able to use show_logs_and_return_non_zero

Add some pulp_rpm specific debug to show_logs_and_return_non_zero

Add more after_failure lines, misc cleanup &, formatting fixes.

Delete the old CI ansible-pulp playbooks.

Accomodate pulp_rpm needing pulp-smash-config.json, but the pulpcore
PR is not ready yet.

Problem: CONTENT_HOST not set when deploying pulp-api
Solution: add content_host to the CR used by pulp-operator
re: #5138
https://pulp.plan.io/issues/5138

History

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

  • Description updated (diff)

Please register to edit this issue

Also available in: Atom PDF