plumbing
plumbing copied to clipboard
tektoncd
Fix peribolos webhook
Expected Behavior
The webhook used by periobolos is configured to webhook.periobolos.dogfooding.tekton.dev.
Actual Behavior
The event listener is set to LoadBalancer mode.
The public IP from the service is not configured as webhook in the commity repo, so no updates happen.
Additional Info
- Change the service type to
NodePort - Setup an ingress, similar to the CI one
- Define the name
webhook.periobolos.dogfooding.tekton.devon Netlify side. We have an open issue about automating this step, so it's manual until that is implemented. - Create the webhook in the community repo. We might want to automate the creation of the webhook too but it's manual for now.
As a side, there is a task for that in the triggers getting started about creating the webhook. We should move that into the catalog, and setup a cronjob that maintains the webhooks using that.
As a side, there is a task for that in the triggers getting started about creating the webhook. We should move that into the catalog, and setup a cronjob that maintains the webhooks using that.
I think https://github.com/tektoncd/catalog/pull/243 does that.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
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.
@afrittoli: Reopened this issue.
In response to this:
/reopen
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.