<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/letsencrypt/letsencrypt-lego, branch stable/2025.2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2025-04-24T13:10:08+00:00</updated>
<entry>
<title>Allow specification of a key type</title>
<updated>2025-04-24T13:10:08+00:00</updated>
<author>
<name>Jay Jahns</name>
<email>jayjahns@gmail.com</email>
</author>
<published>2024-11-11T17:24:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=f1248fe58a2e51a679d033c401e5d8953b04c8da'/>
<id>urn:sha1:f1248fe58a2e51a679d033c401e5d8953b04c8da</id>
<content type='text'>
Letsencrypt allows using a specific key type for certificates. If
the user has an internal letsencrypt mechanism, such as Vault Acme,
then they have to provide a specific key type as the default is
not supported.

This change will allow a user to specify a key type and use the lego
default in the event that they don't specify it.

Partial-Bug: 2087860
Change-Id: I83e618a861b4d51b6a7893f79c50fdfc35228891
</content>
</entry>
<entry>
<title>[letsencrypt] Rename script for updating certificates</title>
<updated>2024-12-18T13:13:55+00:00</updated>
<author>
<name>Michal Arbet</name>
<email>michal.arbet@ultimum.io</email>
</author>
<published>2024-12-03T08:37:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=36ef420f827dd1d8150720f2ab84ddd34c54ca36'/>
<id>urn:sha1:36ef420f827dd1d8150720f2ab84ddd34c54ca36</id>
<content type='text'>
This patch renames the update-haproxy-cert script to
update-loadbalancer-cert to make the name more generic.
The change is necessary because support for ProxySQL
will be introduced in the next patch, requiring a name
that reflects broader applicability.

To keep the diff in the following patch clean and easier
to review, this patch focuses exclusively on the rename.

Change-Id: I15f9b5cf3976f4298cdc7da4530f2d7d09614e88
</content>
</entry>
<entry>
<title>Fix EAB support in letsencrypt</title>
<updated>2024-12-11T18:55:47+00:00</updated>
<author>
<name>Michal Arbet</name>
<email>michal.arbet@ultimum.io</email>
</author>
<published>2024-12-06T22:16:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=6698a072d0169b2ecbad82322821eabd6186d090'/>
<id>urn:sha1:6698a072d0169b2ecbad82322821eabd6186d090</id>
<content type='text'>
This patch fixes recently merged [1] patch.

 - Original patch added params function args
   eab, hmac, key_id, but then
   EXTERNAL_ACCOUNT_BINDING_OPTS var is passed
   into obtain_or_renew_certificate which
   can't work

 - This patch correctly set EXTERNAL_ACCOUNT_BINDING,
   HMAC, KEY_ID defaults and then call obtain_or_renew_certificate
   function with them. This will ensure that arguments are always
   set, so we can write if condtional correctly and process.

[1] https://review.opendev.org/c/openstack/kolla/+/916617

Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/933924
Change-Id: I406ff10edec9dc94b1a3de005080e149ee3ab3f2
</content>
</entry>
<entry>
<title>Add Let's Encrypt EAB support</title>
<updated>2024-12-05T08:21:14+00:00</updated>
<author>
<name>Piotr Parczewski</name>
<email>piotr@stackhpc.com</email>
</author>
<published>2024-04-22T11:33:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=4adc9a103554005a675fd018f965f34701777897'/>
<id>urn:sha1:4adc9a103554005a675fd018f965f34701777897</id>
<content type='text'>
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/935656

Change-Id: I0b20d82a0061062f8aa9dfe179b1d02708ad610e
</content>
</entry>
<entry>
<title>Add mechanism for patching files in containers</title>
<updated>2024-11-15T08:04:30+00:00</updated>
<author>
<name>Michal Arbet</name>
<email>michal.arbet@ultimum.io</email>
</author>
<published>2022-02-15T12:50:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=11f65c6c1d3bfd6a12f8e71d778d46d635010449'/>
<id>urn:sha1:11f65c6c1d3bfd6a12f8e71d778d46d635010449</id>
<content type='text'>
This patch adds a way to patch files in a Docker
image built by Kolla. This is very useful for several
reasons, specifically:

- Custom modifications
- The stable branch of some library has a fix but no pip
  package has been released
- Eliminates the need to package your own pip packages
- Eliminates the need to invent your own versioning to prevent
  upstream versioning
- Eliminates the need to manage a pip server
- In other words, it eliminates the need to get a wheel into
  the image and install it manually using any method not
  previously mentioned

It is also highly desirable because, although Kolla can replace
the source for a service with a custom URL for a tarball or its
own Git repo, it cannot do this for dependencies pulled from pip.

I would also like to point out that this is a feature with its own
code path and works only if the user "inserts" a patch into the folder
patches/docker-image/something.patch and creates an analogous series
file for patch source code.

Simply said, this code will never interfere with the upstream build process
since this feature is not intended for use in upstream.
It is rather meant for downstream users who know what they are doing.
Now they just have an option to patch their images.

Everything works on all layers of the Docker image and stores a report
of applied patches which can then be seen in /etc.

This mechanism is similar as debian patch quilt.

Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
</content>
</entry>
<entry>
<title>Move curl sources to sources.py</title>
<updated>2024-02-21T08:26:52+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2024-02-14T13:02:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=750a137815f1ca58c7e65d23e9d63403ea282b1a'/>
<id>urn:sha1:750a137815f1ca58c7e65d23e9d63403ea282b1a</id>
<content type='text'>
Move most curl sources to sources.py, so it can be automatically
updated in future.

This also makes overriding the versions/locations/sha256 easier.

Change-Id: Ib3497fe96162ae190e5c113cacaaa3ef8334f590
</content>
</entry>
<entry>
<title>Merge "[follow-up] Use full binary path when invoking ip"</title>
<updated>2024-02-02T15:34:36+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2024-02-02T15:34:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=f4edc7e1c15788b87d80513ff255b832b2e41eb5'/>
<id>urn:sha1:f4edc7e1c15788b87d80513ff255b832b2e41eb5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge "Use full binary path when invoking ip"</title>
<updated>2024-01-31T13:27:20+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2024-01-31T13:27:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=d7a03105bf0016e46e60fcc15b7d5a8e4e205cc5'/>
<id>urn:sha1:d7a03105bf0016e46e60fcc15b7d5a8e4e205cc5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[follow-up] Use full binary path when invoking ip</title>
<updated>2024-01-31T12:42:36+00:00</updated>
<author>
<name>Michal Arbet</name>
<email>michal.arbet@ultimum.io</email>
</author>
<published>2024-01-31T12:38:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=f73c6b4c75cebba7c5a4987e25bd7f3db5641854'/>
<id>urn:sha1:f73c6b4c75cebba7c5a4987e25bd7f3db5641854</id>
<content type='text'>
Patch [1] fixed invoking of ip command in
one script but forgot to fix on another place
in another script.

This patch is follow-up path and fix the same
issue in those script.

[1] https://review.opendev.org/c/openstack/kolla/+/906516

Change-Id: I5e41a550e438fb3e4008a9e6b8df35c4775c5c30
</content>
</entry>
<entry>
<title>Use full binary path when invoking ip</title>
<updated>2024-01-24T12:23:52+00:00</updated>
<author>
<name>Piotr Parczewski</name>
<email>piotr@stackhpc.com</email>
</author>
<published>2024-01-24T12:23:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=c3eb169e6c62747cfbc5ddc8ba951f7f5dda6382'/>
<id>urn:sha1:c3eb169e6c62747cfbc5ddc8ba951f7f5dda6382</id>
<content type='text'>
Closes-bug: #2051111
Change-Id: I2a4df6121236379d88d0d7f2f7a888feab273003
</content>
</entry>
</feed>
