-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 boskos stateful set to use RollingUpdate (default @v1) #13594
Conversation
/assign @Katharine |
/lgtm |
LGTM label has been added. Git tree hash: 8320f0242159894b11361ebbdba0d02a25bd5932
|
(feel free to hold cancel when you are around) |
is this going to auto deploy ? |
I don't believe this will auto-deploy. Oncall (currently @mirandachrist) should probably deploy this after it merges. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clarketm, sebastienvas 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 |
Why isn't |
a5411b5
to
09b8e28
Compare
Good point. However in order to deploy this we want to make sure the stateful set is deleted before. Not sure how on call wants to handle this. |
I think it would be best to list the |
correct: |
/hold cancel |
LGTM label has been added. Git tree hash: 81241b6b27cebb3c40a214c02f7719749d3948e4
|
In order to remove the persistent volume, the persistent volume claim also needed to be removed. On the k8s build cluster, this was named
|
Thanks @chases2 |
This change is to make our Boskos deployment consistent with upstream, almost a mirror of kubernetes/test-infra#13594
…#1584) This change is to make our Boskos deployment consistent with upstream, almost a mirror of kubernetes/test-infra#13594
Remove all the persistent volumes things, since we have using CRDs for more than a year now.
Fixes ##11956