Skip to content
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

Bump Kubernetes version to v1.31 and update related dependencies #152

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

012xx
Copy link
Contributor

@012xx 012xx commented Jan 9, 2025

Overview

Bump Kubernetes version to v1.31 and update related dependencies

What

  • update dependencies
  • Automatic updating of files by make check-generate
  • Enabling SkipNameValidation

Why

Regular container updates
k8s 1.31 updated

@012xx 012xx force-pushed the container-updates branch 5 times, most recently from d35cc5c to 91a419c Compare February 21, 2025 03:56
@012xx 012xx marked this pull request as ready for review February 21, 2025 05:22
@012xx 012xx changed the title Update dependencies Bump Kubernetes version to v1.31 and update related dependencies Feb 27, 2025
@012xx 012xx force-pushed the container-updates branch from 91a419c to 2d808cc Compare February 28, 2025 05:54
- name: Set up chart-testing
uses: helm/chart-testing-action@v2.2.1
uses: helm/chart-testing-action@v2.7.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

helm/chart-testing-action is not an action created by a verified creator, so you need to check and specify the full commit hash.
ref. https://github.com/marketplace?query=helm&verification=verified_creator&type=actions

@@ -33,10 +33,10 @@ jobs:
run: ct lint --config ct.yaml

- name: Create kind cluster
uses: helm/kind-action@v1.10.0
uses: helm/kind-action@v1.12.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

helm/kind-action is not an action created by a verified creator, so you need to check and specify the full commit hash.

@@ -37,26 +37,26 @@ jobs:
export TAG=$(curl -s "https://api.github.com/repos/cybozu-go/accurate/releases/latest" | jq -r .tag_name)
echo "GORELEASER_PREVIOUS_TAG=${TAG}" >> $GITHUB_ENV
- name: GoReleaser
uses: goreleaser/goreleaser-action@f82d6c1c344bcacabba2c841718984797f664a6b # v4.2.0
uses: goreleaser/goreleaser-action@9ed2f89a662bf1735a48bc8557fd212fa902bebf # v6.1.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some breaking changes in the goreleaser/goreleaser-action between these versions. Could you describe any actions you took, or if you didn't, please explain the reason?
ref. https://github.com/goreleaser/goreleaser-action/releases

(I guess you dealt with the breaking changes by https://github.com/cybozu-go/accurate/pull/152/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R119.)

Copy link
Contributor Author

@012xx 012xx Mar 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Fixed a deprecated notation in the Makefile.
    goreleaser build --snapshot --rm-dist -> goreleaser build --snapshot --clean
    https://goreleaser.com/deprecations/#-rm-dist
  2. .goreleaser.yaml Version Fixes(Error: “Only version: 2 configuration files are supported, your configuration file is version: 0, please update it”.)
  3. Fixed a deprecated notation in the .goreleaser.yaml
    https://goreleaser.com/deprecations/#archivesformat
    format: tar.gz' -> formats: [ 'tar.gz' ]
hibiki_takehara@ubuntufocal:~/accurate$ 
k8s:minikube> goreleaser check # using latest v2
  • checking                                 path=.goreleaser.yaml
  • 1 configuration file(s) validated
  • thanks for using GoReleaser!
hibiki_takehara@ubuntufocal:~/accurate$ 
k8s:minikube> 

PROJECT Outdated
@@ -1,6 +1,6 @@
domain: cybozu.com
layout:
- go.kubebuilder.io/v3
- go.kubebuilder.io/v4

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file should not be edited manually but with kubebuilder. If you upgrade kubebuilder, you need to follow the migration guide I think.
ref. https://book.kubebuilder.io/migration/v3vsv4

@zoetrope Could you give us your opinion whether to upgrade kubebuilder?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we discussed, please revert the change of kubebuilder from v4 to v3 and leave a comment referring to that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After discussing it as a team, we decided to stick with Kubebuilder version 3. Upgrading would involve significant changes to the directory structure and other areas, with minimal return on investment. For more details, see the reference: https://github.com/kubernetes-sigs/kubebuilder/releases/tag/v4.3.0

@012xx 012xx force-pushed the container-updates branch from 2d808cc to 3b7ef84 Compare March 3, 2025 04:41
@012xx 012xx requested a review from takahiro-yamada March 3, 2025 05:41
PROJECT Outdated
@@ -1,6 +1,6 @@
domain: cybozu.com
layout:
- go.kubebuilder.io/v3
- go.kubebuilder.io/v4

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we discussed, please revert the change of kubebuilder from v4 to v3 and leave a comment referring to that.

@012xx 012xx force-pushed the container-updates branch from 3b7ef84 to 3f05d6a Compare March 3, 2025 07:34
@012xx 012xx requested a review from takahiro-yamada March 3, 2025 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants