The trademark for the logo, as filed, is specified as dark blue.
That logo needs to be displayed in a user guide or manual or
alongside a direct download of the software in order to demonstrate
continued use of the mark, and the foundation's trademark lawyers
have expressed concern that a white version is insufficient (but
they seem to be okay with the current background color as long as
the lines of the logo are colored similar to the version on file).
This is a copy of the equivalent change from the zuul repository.
Co-Authored-By: James E. Blair <jim@acmegating.com>
Depends-On: https://review.opendev.org/934443
Change-Id: I95e31e8ff4e91ef022a08d57b2763c5ec1e39e2d
This change fixes a few CI failures in the zuul-operator
* nox docs: the regex expression wasn't accepted
* version.py was broken because pkg_resources is removed from newer
pythons
* the /api/tenants endpoint no longer appears to return projects or
queue items so the functional test was failing
Change-Id: Ia492fa48ff682454553d9c1b04d4e83b40a276cf
This matches what Zuul and Nodepool are doing. Getting off the older
images will alos allow OpenDev to stop building them. We update the
unittest job to python 3.11 in the process to better cover what people
will deploy.
Change-Id: Id631909640b015ffff9660f33a85c1b1bac375f8
Operator expects a {name,value} object, so we were unable to set envs with the existing CRD schema
Change-Id: Icf81caea3e141c56b0669e901dd1175c2b3465fe
These are mostly CI fixes:
* Use podman+cri-o based minikube:
* This is still considered experimental, but seems to be
more supported than the 'none' driver.
* Fix an issue where ssh to the emulated static node fails:
* PAM needed to be disabled for openssh
* openssh needs more permissions to run - cri-o based minikube
is more strict
* Rebase test container to Fedora 40
* Update the ingress definition to current API version
* Update zookeeper from 3.5.5 to 3.8.4:
* required for nodepool 9.0.0+
* Update the percona operator from 1.11 to 1.14:
* required for kubernetes 1.24+
* Update test node to Ubuntu Jammy from Ubuntu Bionic
* Update minikube to 1.33.1
* Added some more explicit logging to the k8s state, this
could be split off into a role in future.
Depends-On: https://review.opendev.org/c/zuul/zuul-jobs/+/924970
Change-Id: I7bf27750073fa807069af6f85f2689173b278abe
This expands the noxfile to include the linters session and switches
the tox-linters job with the nox-linters job.
Change-Id: If5ff34aded40c66667eaa468baea10fb2658e2b3
Not every cluster has a default storage class and even if they do, we
don't always want to use that default storage class for our persistent
volumes. Instead, allow the user to specific this via the cluster
configuration itself for the three cases we require (zookeeper,
scheduler, and registry).
Change-Id: I948d57ce59d9b16c1c70fc52af2e22bd6131e6e2
Do this to take advantage of python 3.10's speed improvements as
illustrated by Zuul proper. But als OpenDev is looking at dropping
python 3.8 image builds to make room for python 3.11.
Change-Id: I0bb4902d32003ab8e8fb35e6cc39e62ceed88aa8
@kopf.on.update('secrets') will cause us to attempt to listen to
updates to every secret in the Kubernetes cluster in which we are
running. This is negative because:
* kopf annotates every object it is watching to track last known
state, which will be *every secret in the cluster* if with the
current approach. This is a somewhat obnoxious behaviour.
* if the operator is not running with elevated priviledges, this may
not work correctly anyway, although the current deployment does
provide the operator user with cluster-admin priviledges
Instead, we should only track the secrets that we've expressed
interest in, which is effectively what we're doing anyway, but this
will save us from annotating every secret in the cluster.
Change-Id: I540841ee8b053ae05ca7943aca3f1646b509cfd9
Upgrade from 1.30.* to 1.35.0 or later. The minimum bound is
introduced because earlier versions of kopf may not work correctly
with the operator.
Change-Id: I2b40e223f48aca6f45d901e1cc1ee67cf27e486f
If we leave the value has as the result of b64decode(), we end up with
a bytes-like object that gets serialized into our zuul.conf as
b'.....', which is likely not what we actually want. Instead, assume
this is a utf-8 encoded value and decode it that way.
Change-Id: Ie61ad82c022888000e72bedfea99123dda34d5c0
This change enables installing the zuul-operator on a recent cluster,
where CRD are no longer beta:
- Update apiVersion in the CRD
- Update cert-manager to v1.8.2
- Update pxc to v1.10.0
- Add openAPIV3Schema to zuul crd (from https://review.opendev.org/c/zuul/zuul-operator/+/800302)
Change-Id: I12ac02d609ea6a2806c734ca00023e4d1059af37
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
A variable reassignment in conf.py caused errors when we try to build
release versions of docs. Correct that by swapping the order of use
and assignment.
Change-Id: I971b04156e8e7be18fdec6859e4b696f5dd3d7da
Since we support custom image prefixes, we should also support
imagePullSecrets since they are likely to be in a private registry.
This also updates some nearby documentation which was out of date.
Change-Id: Id43382284a9adde877e2383644a31bda24030b2b
* 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
We are supposed to update zuul/nodepool when the relevant secrets
are updated. We do that by subscribing to changes on all secrets
in the system, then check to see if they are ones that we're watching
and if so, run the appropriate operator methods.
We only updated the list of secrets to watch on startup, which means
that from a clean start where a zuul was added, we would not add
the new secrets to our list. This change updates the list after every
time that the zuul resource is created or updated.
Change-Id: Ib6191367eb2596eba560b9c570140f33866c005f
So that we can better test functions related to ssh connectivity,
add a static node to the functional test.
Change-Id: I3dfdaca0b4e5dbfb35e4a645c7bcb56e0eec88c2
