-
Notifications
You must be signed in to change notification settings - Fork 110
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
Change Boskos StatefulSet to Deployment. #225
Change Boskos StatefulSet to Deployment. #225
Conversation
Hi @tomgeorge. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
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.
Thank you for this!
To be honest I don't fully understand the ramifications of dropping the PVC here, but since this change replicates what was done on the infra side, I think it's good.
/lgtm
Sorry for the delay. I wasn't super sure either, I had faith that test-infra did the right thing 😅 Looking into it a little more, I think Boskos keeps a list of resources that are stored in the PVC. See https://github.com/kubernetes/test-infra/blob/2ec0aac72450a8617baf78066a08bb7e943289ee/boskos/common/common.go#L103 for the definition of the The storage plugin for boskos adds/removes those Boskos added the ability to store that user data as CRDs, so I think going forward they have migrated to that. The Resource information (Name, Type, Last Updated, etc) are stored in the API server. |
To clarify, it's storing the current state of Boskos and the resources under management |
/hold /approve @tomgeorge @afrittoli @bobcatfish do we want to move ahead on this issue & PR? Any outstanding questions or problems before we merge? |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
From my investigation in #566, I think we should be able to move to a Deployment from a Stateful set with no issues. Specifically: #566 (comment) |
boskos/boskos.yaml
Outdated
@@ -91,31 +73,19 @@ spec: | |||
- name: boskos | |||
image: gcr.io/k8s-prow/boskos/boskos:v20200117-6384054e3 | |||
args: | |||
- --storage=/store/boskos.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.
This would have prevented #566
/kind cleanup |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
@tomgeorge feel free to cancel the hold if you want to proceed with this PR! |
/hold cancel |
/test plumbing-yamllint |
This change deploys Boskos as a Deployment rather than a StatefulSet, to enable quicker feedback in the deployment process, and removing the need to delete the Boskos pods before new pods are started. This addresses tektoncd#193 Signed-off-by: Tom George <tg82490@gmail.com>
cb2416d
to
172c14c
Compare
/lgtm |
Changes
This change deploys Boskos as a Deployment rather than a StatefulSet, to enable quicker feedback in the deployment process, and removing the need to delete the Boskos pods before new pods are started.
This addresses #193
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.