kubernetes-sigs / tejolote Goto Github PK

What happened:

https://github.com/kubernetes-sigs/tejolote/blob/main/pkg/store/driver/gcs.go is used to publish artifacts to the current GCS bucket using the google storage package. However, a new community-owned bucket is currently being rolled out to replace the GCS bucket and uses an https endpoint that can redirect to potentially other backend storage providers. Tejolote should support being able to upload artifacts via an http interface as well as the curreng GCS implimentation.

ref: kubernetes/k8s.io#2396
Note: writing content to the new endpoint (dl.k8s.io) is not currently supported but will be in the future kubernetes/k8s.io#2396 (comment)

What happened:

• As part of the kubenetes-sigs/karpenter release process, we run tejolote to attestations to the release. We saw our release runs fail on tejolote. We have perviously ran tejolote with the same version and everything seemed to run as expected.
• https://github.com/kubernetes-sigs/karpenter/actions/runs/8514270400/job/23319674249
• Looking for some guidance in identifying the issue.

What you expected to happen:

• We expect the run to complete successfully

How to reproduce it (as minimally and precisely as possible):

• This would the GitHub action we run, we have not changed anything in our configuration when doing 3 other release for Karpenter

Anything else we need to know?:

Environment:

• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What would you like to be added:

Add prow to the supported build systems.

Why is this needed:

Lots of build processes in Kubernetes and the cloud native world run on Prow. We need to add support for prow as a build system to enable attesting those builds.

At the end:

"Both build system runs and artifact repositories are specified by using spec urls that point to the specific runs and storage location. Check out the"

Sentence not complete, and link broken.