-
Notifications
You must be signed in to change notification settings - Fork 813
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
Issue template for Kubernetes Upgrades #2606
Issue template for Kubernetes Upgrades #2606
Conversation
Build Failed 😱 Build Id: d9f8ca16-0560-43f5-82f1-7bd16ea41b28 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
e2e stable, TestFleetRollingUpdate - flake |
Build Succeeded 👏 Build Id: dddff719-91e2-471a-ba35-5e8abce0c833 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
- [ ] Kind | ||
- [ ] Update client-go | ||
- [ ] Update CRD API reference | ||
- [ ] Update links to k8s documentation in site/assets/templates/crd-doc-config.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you surround the filename here in backticks (like you did on lines 21-22)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
name: Upgrade Kubernetes Version | ||
about: Issue for updating the Kubernetes version (usually decided in community meetings). | ||
title: 'Update Kubernetes to {version}' | ||
labels: kind/operations, kind/feature |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I usually mark these as kind/breaking
since we our current upgrade strategy is pretty disruptive. However, I'm ok marking the issue as a feature and the PRs as breaking if that generates better release notes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No that's a really good point. It should be breaking. I'll make that tweak.
Build Failed 😱 Build Id: 13120e16-5c24-4f70-bcd2-11eedb763632 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
This came up on a community call, so I'm finally putting it together 😄
4d4697f
to
c14aa1c
Compare
Build Failed 😱 Build Id: 342e8a5b-7b21-47bf-9e56-385b0b9285d6 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 2473156b-a2b1-44f5-81cb-6f5f617e8315 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
This came up on a community call, so I'm finally putting it together 😄
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
N/A