This change tries to fix the following issue:
kubernetes.config.config_exception.ConfigException: Invalid kube-config file. No configuration found.
This change also provides input to the wsdump test to prevent the
command from hanging when testing the console stream connection.
Change-Id: I4880e0420b7a66639258aa84a8d61b5620313ee3
* Pin minikube to 1.22.0
Version 1.23.0 is failing with
error: unable to recognize "deploy/crds/zuul-ci_v1alpha2_zuul_crd.yaml":
no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
Until we learn more, pin to the previously working k8s version.
* Add debug log-level to the podman login test command
This change should improve the test failure debugging where it
currently may just prints "Shutting down, got signal: Terminated".
* Remove "https://" from registry login
f8136e70f9
Added path-based authentication to "podman login" which they argue
is incompatible with including https:// in the registry identifier.
Doing so now produces an error.
Co-Authored-By: Tristan Cacqueray <tdecacqu@redhat.com>
Change-Id: Ic44b56a2eb6ac15cc5f4af5312fa4e3956d6e457
The log line that we should wait for has changed in Zuul; this is
the new equivalent.
Change-Id: I34fc52729fa64bb36c72fe6661f0794620a25092
Depends-On: https://review.opendev.org/c/zuul/zuul/+/804806
So that we can better test functions related to ssh connectivity,
add a static node to the functional test.
Change-Id: I3dfdaca0b4e5dbfb35e4a645c7bcb56e0eec88c2
This is the test setup I have used to run the functional tests
locally. In particular, the restart.sh script is useful for
very quickly rebuilding the cluster from scratch while also
using the local docker image cache to populate the cluster with
cached images for speed.
Change-Id: I994de1cdd49b487d68083f6e01ba73bfc4274d05
We overrode the PXC resource values in order for functional tests
in minikube to work. Restore the defaults and set an override in
the functional tests.
Change-Id: Id0560d9089f03ddcb116dccec0b424b811186d65
The test is moved from run.yaml to test.yaml to benefit from the cluster_ip
variable that is set at the start of test.yaml.
Change-Id: Ia0d1cbac94b6b638b6f410d9647ee1822751a767
Allow the user to specify an image prefix and a version tag.
This updates the functional test to account for a recent change
in Zuul which returns incomplete builds on the API endpoint.
Change-Id: I49e82c790a518c1c9f5a463250b5b785eacde55a
The operator currently creates an ingress object, but this was really
just to aid testing. The operator probably shouldn't really create one
since doing so may be site-specific.
Having the ingress greatly aids local and functional testing though, so
move it to the functional test playbook.
Change-Id: Ic6296120f8c107ecc29556fdab4d6cddb5216a50
To make the functional tests easier to run locally, run a git server
in k8s instead of on the local machine.
Also, update the secret creation to work with kind as well as minikube.
Change-Id: I4c00129c7105405b0f6256e769486e79c0b173fe
This switches from the ansible/dhall operator framework to kopf,
an operator framework written in pure Python. This allows us to:
* Build the operator application as a Python app.
* Build the operator image using the opendev python builder images.
* Run the operator as a Python CLI program "zuul-operator".
* Write procedural Python code to handle operator tasks (such as
creating new nodepool launchers when providers are added).
* Use Jinja for templating config files and k8s resource files
(direct pythonic manipulation of resources is an option too).
The new CR nearly matches the existing one, with some minor differences.
Some missing features and documentation are added in the commits
immediately following; they should be reviewed and merged as a unit.
Also, fx waiting for scheduler to settle in functional test since
we changed this log line in Zuul.
Change-Id: Ib37b67e3444b7cd44692d48eee77775ee9049e9f
Change-Id: I70ec31ecd8fe264118215944022b2e7b513dced9
This change fixes an issue where zuul services can't create
a lockfile.
Another issue happening with older operator-framework and newer
kubernetes version is being fixed by updating the operator-framework
following this migration documentation:
https://sdk.operatorframework.io/docs/building-operators/ansible/migration/
Change-Id: I6adfb907184112f0b7debb050975f76cd1dd4b01
This change ensures the pip tool is installed as it is no longer
provided by the OpenDev test instance.
Change-Id: Ie9ebf946fbf847f5574c3e140f43bdb1c9949137
This change adds an optional preview configuration to the spec:
preview:
image: docker.io/zuul/zuul-preview:latest
count: 0
Change-Id: Id9d902b3b9f25b1bf3fa459634396d7520681417
This change adds a Cerficiate resource to manage
the registry tls secret with the cert-manager service.
This change also splits the registry rw user to a
dedicated secret to enable separate creation of the passwords.
Change-Id: I673ea8db31fd2926c82a4288fd9362f225794da8
This change adds a new input toggle to enable using a cert-manager service.
The operator currently only setup a selfSigned CA.
Change-Id: Ifc63768a87f9508c66e4414d5286bae2969985e7
This change adds an optional registry configuration to the spec:
registry:
image: docker.io/zuul/zuul-registry:latest
count: 0
storage-size: 20
public-url: https://registry:9000
The operator expect a {{ cr_name }}-registry-tls secret to be provided
for tls and user configuration. If the secret is missing, the operator
creates self signed certificates and generates the user password.
Depends-On: https://review.opendev.org/710644
Change-Id: I0c054485b0ad01d53ddcff93f7bcbf34d1810325
In some case, the test node needs more time to pull the
zuul image. This change increases the wait time to 8 minutes
to prevent false positive failure.
Thsi change also:
* adds a build artifact with the generated kubernetes resources.
* redirects post commands output to logfiles to unclutter the
job-output console.
* replaces kubectl wait by rollout status.
* wait for operator and nodepool-launcher deployment.
Change-Id: I1c499bd11576f92b98511cd1ff180026b8aa70d8
This change updates the external_config and job_volumes attribute
name to be consistent with kubernetes definitions.
Depends-On: https://review.opendev.org/707190
Change-Id: I168128e543e03935c03ab9547f208f18e432e0fc
This change implements https://review.opendev.org/706639
to support custom volume to be mounted in job context.
Change-Id: Ic4a6a27707205594910ad90a5577fbbe727e2352
This change enables using real kubernetes pod label
for the integration tests.
Depends-On: https://review.opendev.org/715308
Change-Id: I24448bf1edb6c546475796a06cf8cbe456716c32
This change adds a new run playbook to perform some integration
tests:
- add a config project with a periodic pipeline
- ensure the executor run a job
- ensure the job results are published in the db
- ensure the console-stream is working
Change-Id: I85187c741b376eaafdef1066452f13e2853caed7
This change replaces the existing tasks with a dhall function to
generates all the kubernetes objects. The operator nows converts
the CR spec to a dhall `Input`, then it applies the function
output to the cluster. Follow-up changes demonstrate how
runtime operations can be performed around that function.
This change updates the zuul-ci_v1alpha1_zuul_cr.yaml file with
the actual CR defined in the zuul specification so that it can
be used in the functional tests.
Depends-On: https://review.opendev.org/702753
Change-Id: Iea51bccf90def6e827d2c5846ad6a7e4c86a5bc1
Tristan Cacqueray