Story #5138
closed
Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io
In pulp-operator, the content_origin should be set to the actual accessible service URL
100%
Description
In pulp-operator, set the pulp_settings.content_origin ($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.
Added by dkliban@redhat.com over 5 years ago
Added by Mike DePaulo over 5 years ago
Revision 20e2315b | View on GitHub
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
Updated by mdepaulo@redhat.com about 5 years ago
- Subject changed from In pulp-operator, the pulp_content_host should be set to the actual accessible service URL to In pulp-operator, the content_origin should be set to the actual accessible service URL
- Description updated (diff)
Added by Mike DePaulo about 5 years ago
Revision c7ee477c | View on GitHub
Set content_origin to the 1st node's 1st address.
If not set by the user.
Limited scope (single-node clusters), but sufficient for minikube/k3s/our Travis CI. fixes: #5138 In pulp-operator, the content_origin should be set to the actual accessible service URL https://pulp.plan.io/issues/5138
re: #5629 [Epic] Introduce CONTENT_ORIGIN as a required setting https://pulp.plan.io/issues/5629
Updated by mdepaulo@redhat.com about 5 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
Implemented, but only for for nodeports of single-node clusters:
https://github.com/pulp/pulp-operator/pull/27
Will be implemented later for multi-node clusters via ingresses:
https://pulp.plan.io/issues/5657
And for load balancers, when available:
https://pulp.plan.io/issues/5683
Updated by bmbouter about 4 years ago
- Category set to Operator - Moved to Github Issues
.
Problem: can't specify CONTENT_HOST setting
Solution: add CONTENT_HOST to the config map
re: #5138 https://pulp.plan.io/issues/5138