Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K3s travis #7

Merged
merged 8 commits into from
Jul 23, 2019
Merged

K3s travis #7

merged 8 commits into from
Jul 23, 2019

Conversation

mikedep333
Copy link
Member

@mikedep333 mikedep333 commented Jul 16, 2019

I developed an alternative solution for:

https://pulp.plan.io/issues/5061
Develop a script to launch 4 pulp containers in just Docker/Podman

In order to implement this, I had to partially implement:
https://pulp.plan.io/issues/5136
pulp-operator needs a stable & configurable accessible port
https://pulp.plan.io/issues/5137
pulp-operator needs configurable and expandable storage size

And some other changes like the postgresql image change.

I also cleaned up some code.

The scripts that content plugin devs would run (in Travis as early phases like install, which Travis collapses the output of) for testing their plugins in containers are:

  1. .travis/k3s-install.sh
  2. up.sh
  3. .travis/pulp-operator-check-and-wait.sh

They would also depend on a minority of other files in the repo existing. I think only the deploy directory.

Note that pulp-operator's image is not automatically built and used. Doing so is task #5174 Currently, the developer has to build and push (per README.md).

Also, as soon as this is merged, I need to do a separate PR to have deploy/operator.yml use the latest tag rather than the k3s-travis tag. Or I need to build the image and push it with the latest tag after review, and do the commit as part of this PR. (This limitation will be addressed later as part of #5174 & #5175.)

…try.centos.org

This fixes k3s being unable to download it from registry.centos.org,
which is due to either the fact that it requires the docker:// v1 protocol,
or it being an insecure registry.

It seems to be the same image, but newer by 1 month & a small diff in
size.
Both by CentOS themselves. Same args.

We cannot use the RHEL8 postgres image because it is publicly searchable
but not publicly accessible.

Note that an attempt was tried to use docker://registry.centos.org as the image
name, but it randomly stopped working (STATUS: InvalidImageName)
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
Add different ConfigMaps for known use cases like Travis

Partially implements:
ref #5137
https://pulp.plan.io/issues/5137
@mikedep333 mikedep333 changed the title [WIP] K3s travis K3s travis Jul 23, 2019
@dkliban dkliban merged commit 65a9085 into pulp:master Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants