-
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
Configure liveness and readiness probes for prow-controller-manager. #24340
Configure liveness and readiness probes for prow-controller-manager. #24340
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, cjwagner 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 |
@@ -22,6 +22,11 @@ metadata: | |||
spec: | |||
# Mutually exclusive with plank. Only one of them may have more than zero replicas. | |||
replicas: 1 | |||
strategy: |
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.
would be nice to also add comment here as being done below. However not worth blocking
/unhold |
Follow up to #24042
Since the previous PR,
prow-controller-manager
can now have a slower startup due to retrying build manager creation. This PR should change the deployment strategy to allow two pods to coexist during deployment and it should make the rolling deployment strategy aware of when the build managers are ready for use so that the old pod is not removed until the new pod is ready.I just ready all the k8s docs I could find on liveness/readiness probes and a couple articles about potential pitfalls. I think this configuration should give us the behavior we want without risk of crashlooping.
/assign @alvaroaleman @chaodaiG
/hold