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

chore(operator): Upgrade operator-sdk 1.37.0 and kind 0.23.0 #14445

Merged
merged 2 commits into from
Oct 14, 2024

Conversation

periklis
Copy link
Collaborator

What this PR does / why we need it:
Follow up on #14416 to upgrade the used operator-sdk and kind for local development.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

@@ -7,7 +7,7 @@ spec:
spec:
containers:
- name: kube-rbac-proxy
image: gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0
image: gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why was this also updated? And why v0.16.0? It seems like v0.18.0 is the one aligned with k8s v1.30

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@JoaoBraveCoding Following the migration steps from v1.33 up to v1.37 I was instructed to update to v0.16 here: https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.36.0/

You say [email protected] is using the [email protected] client-go/api then we can update to this one too. I need to double check what version we issue on OCP v4.17 though.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I see! Yes according to the release notes that seems to be the case https://github.com/brancz/kube-rbac-proxy/releases

Copy link
Collaborator

@JoaoBraveCoding JoaoBraveCoding left a comment

Choose a reason for hiding this comment

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

lgtm

@periklis periklis merged commit 8d6da6d into grafana:main Oct 14, 2024
68 checks passed
periklis added a commit to periklis/loki that referenced this pull request Oct 18, 2024
periklis added a commit to openshift/loki that referenced this pull request Oct 18, 2024
periklis added a commit to periklis/loki that referenced this pull request Oct 21, 2024
openshift-merge-bot bot added a commit to openshift/loki that referenced this pull request Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants