This PR updates the yaml linter configuration
to align it with what we have in the osh-infra
repo.
Change-Id: I3585fdc6663b2ae7bfb5c1d8a13672ac3055bf86
Loci builds Openstack images nightly and publishes
them to both Docker Hub registry and to Quay registry.
Quay registry has much more tolerant rate limits, so
for users it is more convenient to use quay.
Change-Id: Id5c8776202a8c10a7aebccdae174880743dbdd09
This is the action item to implement the spec:
doc/source/specs/2025.1/chart_versioning.rst
Depends-On: I327103c18fc0e10e989a17f69b3bff9995c45eb4
Depends-On: I7bfdef3ea2128bbb4e26e3a00161fe30ce29b8e7
Change-Id: I4974785c904cf7c8730279854e3ad9b6b7c35498
Use quay.io/airshipit/kubernetes-entrypoint:latest-ubuntu_focal
by default instead of 1.0.0 which is v1 formatted and
not supported any more by docker.
Change-Id: Idf43d229d1c81c506653980b5e8cd6463550bc5f
- In some charts third party images are used.
Need inspection which of them can be updated.
- For some charts we don't build images.
For this case let's build images for active
projects and probably retire charts for retired
or inactive projects.
Change-Id: Ic9e634806d40595992d68c1fc3cd54b655ca5d02
If application credentials with access rules are required,
an OpenStack service using keystonemiddleware to authenticate
with keystone, needs to define service_type in its configuration
file.
Change-Id: I7034e82837d724f12d57969857f79d67c962cebe
Based on spec
support-OCI-image-registry-with-authentication-turned-on.rst
Each Helm chart can configure an OCI image registry and
credentials to use. A Kubernetes secret is then created with this
info. Service Accounts then specify an imagePullSecret specifying
the Secret with creds for the registry. Then any pod using one
of these ServiceAccounts may pull images from an authenticated
container registry.
Related OSH-infra change:
https://review.opendev.org/c/openstack/openstack-helm-infra/+/848142
Change-Id: I54540f14fed29622bc5af8d18939afd06d65e2d8
