-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Update operator.yaml
and add schedule backup example
#15969
Conversation
Signed-off-by: Florent Poinsard <[email protected]>
Review ChecklistHello reviewers! 👋 Please follow this checklist when reviewing this Pull Request. General
Tests
Documentation
New flags
If a workflow is added or modified:
Backward compatibility
|
Signed-off-by: Florent Poinsard <[email protected]>
@@ -1,4 +1,3 @@ | |||
--- | |||
apiVersion: apiextensions.k8s.io/v1 |
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.
The file is a copy of the output we get when generating the operator.yaml
file in the vitess-operator repository, on top of the PR planetscale/vitess-operator#553
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.
Rest LGTM
--- | ||
apiVersion: scheduling.k8s.io/v1 | ||
description: The vitess-operator control plane. | ||
globalDefault: false | ||
kind: PriorityClass | ||
metadata: | ||
name: vitess-operator-control-plane | ||
value: 5000 | ||
--- | ||
apiVersion: scheduling.k8s.io/v1 | ||
description: Vitess components (vttablet, vtgate, vtctld, etcd) | ||
globalDefault: false | ||
kind: PriorityClass | ||
metadata: | ||
name: vitess | ||
value: 1000 |
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 don't think we want to remove this.
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.
We are not removing this block, the tool moved it a bit earlier in the file. I have used the raw output of kustomize
which I think is what we should do from now on to avoid any conflict or unnecessary changes in the future.
Added "Do not merge" because the operator PR needs to be merged first, then this one, and then the website PR. |
Signed-off-by: Florent Poinsard <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15969 +/- ##
==========================================
- Coverage 68.45% 68.22% -0.23%
==========================================
Files 1562 1541 -21
Lines 197057 197254 +197
==========================================
- Hits 134891 134585 -306
- Misses 62166 62669 +503 ☔ View full report in Codecov by Sentry. |
DCO is working wrong right now, manually verified signoff |
Description
This Pull Request adds one more step to the operator example: schedule backup. It comes at the very end of the guide, after
Resharding
. For this a new401_
file is added.The
operator.yaml
file is also modified to reflect the changes brought by planetscale/vitess-operator#553.Related Issue(s)