Release v1.8.1

[imjasonh]

Notable changes since v1.8.1:

• Use canonical platform values. Fix 1995. #2025 <-- bug fix
• Fix image tags in release workflow #1977 <-- release fix
• Move and fix GetContainerRuntime check from bpfd proc #1996 <-- bug fix
• feat: kaniko dir config option #1997 <-- new feature

All changes: v1.8.0...main

There may also be some auth issues (#1821) but I probably won't have time to dig into them immediately, and the fixes above seem worth releasing.

[chuangw6]

Thanks @imjasonh! Thanks to all contributors on this v1.8.1 release!
#2029

[hojo0590]

Will there be a v1.8.1-debug tag too? Currently there is only debug.
I'd like to test upgrading an image in a CI pipeline but in a safe way.

[imjasonh]

Will there be a v1.8.1-debug tag too? Currently there is only debug. I'd like to test upgrading an image in a CI pipeline but in a safe way.

It looks like the release workflow tagged the debug image as :v1.8.1 instead of as :v1.8.1-debug, based on logs here: https://github.com/GoogleContainerTools/kaniko/runs/5833880413?check_suite_focus=true#step:11:8

This was supposed to take the other branch, based on if [[ debug -eq "latest"]], but for some reason took the branch that tags the image as :v1.8.1. 🤔

The :slim image did the same thing, tagging as :v1.8.1 instead of :v1.8.1-slim: https://github.com/GoogleContainerTools/kaniko/runs/5833880816?check_suite_focus=true#step:11:8

The :latest image correctly points to :v1.8.1 at least, so that's unaffected.

It looks like we need to do some manual intervention, and fix the release workflow for future releases.

crane cp gcr.io/kaniko-project/executor@sha256:3bc3f3a05f803cac29164ce12617a7be64931748c944f6c419565f500b65e8db gcr.io/kaniko-project/executor:v1.8.1-debug

crane cp gcr.io/kaniko-project/executor@sha256:befa11c3531a8c4dab403250c4ce8d770a6b3097054a7d924802d340e687851c gcr.io/kaniko-project/executor:v1.8.1-slim

[chuangw6]

Thanks for pointing out this. @hojo0590
For v1.8.1, I've manually added v1.8.1-debug and v1.8.1-slim. Please try pull with new tags.

Thanks @imjasonh for fixing this in release tagging workflow for future releases.

[hojo0590]

Thanks for pointing out this. @hojo0590 For v1.8.1, I've manually added v1.8.1-debug and v1.8.1-slim. Please try pull with new tags.

Thanks @imjasonh for fixing this in release tagging workflow for future releases.

Thank you for fixing the tags. Pulling the v1.8.1 debug is now possible.