-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Chore]: Start building operator images using bake #6804
Comments
sxd
added a commit
that referenced
this issue
Feb 7, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
This was referenced Feb 7, 2025
sxd
added a commit
that referenced
this issue
Feb 7, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 7, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 11, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 11, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 17, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 17, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 18, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 19, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 19, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 19, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
sxd
added a commit
that referenced
this issue
Feb 20, 2025
Closes #6804 Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue already for this bug?
I have read the troubleshooting guide
I am running a supported version of CloudNativePG
Contact Details
No response
Version
1.25 (latest patch)
What version of Kubernetes are you using?
1.32
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
YAML manifest
What happened?
We're currently using plain docker build and Dockerfile to build the container images for the operator, we should start using bake which will attach the attestation with sboms and everything in one step without adding more actions or process in the middle.
We should also add the signature of these images just like we do for postgres containers
Cluster resource
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: