release version 0.1.4

[jkh52]

We should tag a new version: 0.1.4.

Changes since 0.1.3: v0.1.3...master

Noteworthy:

• #494 (proxy-server and proxy-agent): quiet more error logs
• #498 proxy-server: change --delete-existing-uds-file default to true.
• #505 (proxy-server and proxy-agent): bump k8s dependencies to 1.27
• #485 proxy-agent: smarter readiness check
• #511 proxy-server: fix broken metric frontend_write_duration_seconds

[ipochi]

@jkh52 I'd like a walkthrough of the process when you cut a new release. I'm happy to pick up the next tag release.

[jkh52]

@jkh52 I'd like a walkthrough of the process when you cut a new release. I'm happy to pick up the next tag release.

I follow the steps at RELEASE.md, and there shouldn't be anything not documented there or mysterious.

I think only repository admins have the permissions needed to create tags or branches. I have not yet done steps 2 or 3, would you like to do those for 0.1.4?

(For 0.1.3: step 2 was only just merged, and I never started step 3. I think it's ok to leapfrog from 0.1.2 to 0.1.4 in kubernetes at head.)

[nox-404]

Hey,
I noticed the v0.1.4 tag is present, but the image hasn't been published
https://explore.ggcr.dev/?repo=registry.k8s.io%2Fkas-network-proxy%2Fproxy-agent

[jkh52]

I noticed the v0.1.4 tag is present, but the image hasn't been published

Yes, it's a human step so there is some delay.

/assign @ipochi

@ipochi do you want to take steps 2 and 3 (step 2 is the images publish mentioned here)? If you don't have time, please assign back to me.

[ipochi]

Sure. I'll look at it in the morning.

[ipochi]

@jkh52
Done:

kubernetes/k8s.io#5731
kubernetes/kubernetes#120029

[ipochi]

@jkh52

Why are the steps mentioned in RELEASE.md not idempotent ?

./hack/pin-dependency.sh sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.1.4
./hack/update-codegen.sh
./hack/update-vendor.sh

[jkh52]

FYI today I made some additional release progress, put notes in #523.

[jkh52]

No more actionable here.