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

Prepare 0.31.0 release #1851

Open
19 tasks done
tkatila opened this issue Sep 25, 2024 · 6 comments
Open
19 tasks done

Prepare 0.31.0 release #1851

tkatila opened this issue Sep 25, 2024 · 6 comments
Assignees

Comments

@tkatila
Copy link
Contributor

tkatila commented Sep 25, 2024

Checklist:

  • run validation on main
    • GNR (IAA, DSA)
    • GNR-D (QAT)
    • FPGA
    • SPR (SGX, QAT, GPU, IAA, DSA)
  • Make sure kube-rbac-proxy is the latest version
  • create release-0.31 branch
  • release branch changes
    • edit default_labels.docker + make dockerfiles
    • make set-version TAG=0.31.0 + commit
    • update publish.yml to create docs for v0.31
  • draft release notes, review
  • publish release
  • main branch changes: Post 0.31 updates #1859
    • update base README for supported versions and docs URL
    • update main branch's operator CRs to point to 0.31, also reconciler.go
  • update helm chart: Device plugins 0.31 helm-charts#61
    • Make sure to update CRDs and README
  • update operatorhub.io bundle
@tkatila tkatila self-assigned this Sep 25, 2024
@mythi
Copy link
Contributor

mythi commented Sep 30, 2024

  • update operatorhub.io bundle

we're now back to #1731 (comment)

@tkatila
Copy link
Contributor Author

tkatila commented Oct 1, 2024

I added a section about the operatorhub bundle to the release notes.

@tkatila
Copy link
Contributor Author

tkatila commented Oct 1, 2024

I added a section about the operatorhub bundle to the release notes.

Nevermind. I'll remove it.

@hj-johannes-lee
Copy link
Contributor

@mythi
Copy link
Contributor

mythi commented Oct 1, 2024

k8s-operatorhub/community-operators#5088 k8s-operatorhub/community-operators#5091 Done!

since this moved to stable channel, did you check the upgrade/promotion flows are done correctly?

@hj-johannes-lee
Copy link
Contributor

hj-johannes-lee commented Oct 4, 2024

#1865
I found out that actually the upgrade has not been working properly since sha256 was introduced.

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

No branches or pull requests

3 participants