Release the newest Sealed Secrets version using the Bitnami container release #1392
Conversation
… release With these changes, we are going to check if the Bitnami Container Release process has generated the containers using the tag of with our release. Then, we will generate the official release in our project. Why this decision? Using the Bitnami Release process, the containers are tested in several environment (OpenShift, AKS, etc) running our integration tests. From the user side, you will not see any change at all. We are publishing the containers in the same registry and our chart and controller will use same containers. Signed-off-by: Alvaro Neira Ayuso <alvaron@vmware.com>
alvneiayu
force-pushed
the
releaseprocessbitnami
branch
from
7c27d19
to
c2a0914
Compare
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
|
Due to the lack of activity in the last 7 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary. |
Signed-off-by: Alvaro Neira Ayuso <alvaron@vmware.com>
alvneiayu
force-pushed
the
releaseprocessbitnami
branch
from
72aa493
to
d9c8007
Compare
There is : docker image with tag v0.25.0 doesn't exists (while v0.24.5 does). |
|
hi @sathieu. The new images will be published without the v from now. You can find the image 0.25.0 instead of v0.25.0. Thanks Álvaro |
With these changes, we are going to release the newest Sealed Secrets version using the containers generated by the Bitnami Container Release process using the tag of with our release. Then, we will generate the official release in our project.
Why this decision? Using the Bitnami Release process, the containers are tested in several environment (OpenShift, AKS, etc) running our integration tests. Like this, the project will be covered in several real environments that Sealed Secrets in running by the users.
From the user side, you will not notice any change at all. We are publishing the containers in the same registry and our chart and controller will use the same containers.
fixes #1393