Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automate obtaining a test cluster #137

Closed
afrittoli opened this issue Dec 2, 2019 · 9 comments
Closed

Automate obtaining a test cluster #137

afrittoli opened this issue Dec 2, 2019 · 9 comments
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/test-infra Issues or PRs related to the testing infrastructure kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
dogfooding

Comments

@afrittoli
Copy link
Member

Expected Behavior

We need a Tekton based way to obtain a test cluster for testing, e.g. when doing a release we need a test cluster to test the release against.

Actual Behavior

At the moment we can either use a pre-provisioned cluster or use test-infra tools to claim a cluster from Boskos, but that's not very "Tektonik".
I was thinking we could have one (or both):

  • an interceptor that can allocate a test cluster and enrich the binding with the name of a cluster resource that embeds credentials for access
  • a tekton task that allocates the cluster (from Boskos? from scratch?) and builds the cluster resource

How do we cleanup the cluster once the job is done? I guess in a similar way we could trigger cleanup once the test pipeline is complete. We might also need a way to garbage collect them in case of missed signalling.

Steps to Reproduce the Problem

Additional Info
@vdemeester vdemeester added area/test-infra Issues or PRs related to the testing infrastructure kind/feature Categorizes issue or PR as related to a new feature. labels Dec 3, 2019
@vdemeester vdemeester mentioned this issue Dec 13, 2019
Closed
@vdemeester vdemeester added the area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) label Dec 13, 2019
@bobcatfish bobcatfish added this to Needs triage in Tekton Pipelines Feb 26, 2020
@vdemeester vdemeester moved this from Needs triage to Backlog in Tekton Pipelines Mar 16, 2020
@bobcatfish bobcatfish mentioned this issue Apr 2, 2020
Open
@vdemeester vdemeester added this to To do in dogfooding Apr 16, 2020
@vdemeester vdemeester removed this from Unsure what to do next in Tekton Pipelines Apr 16, 2020
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 13, 2020
@tekton-robot
Copy link
Contributor

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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.

@tekton-robot tekton-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 13, 2020
dogfooding automation moved this from To do to Done Aug 13, 2020
@vdemeester
Copy link
Member

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

@bobcatfish I think this is "kinda" done through the boskos tasks in the catalog ?

@tekton-robot tekton-robot reopened this Aug 13, 2020
dogfooding automation moved this from Done to In progress Aug 13, 2020
@tekton-robot
Copy link
Contributor

@vdemeester: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

@bobcatfish I think this is "kinda" done through the boskos tasks in the catalog ?

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.

@tekton-robot tekton-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 13, 2020
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2020
@bobcatfish
Copy link
Contributor

@vdemeester i agree we could use the boskos Task for this! seems fine to me to close :D

dogfooding automation moved this from In progress to Done Nov 11, 2020
@bobcatfish
Copy link
Contributor

That's https://github.com/tektoncd/catalog/tree/master/task/boskos-acquire/0.1 for context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/test-infra Issues or PRs related to the testing infrastructure kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
dogfooding
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vdemeester @bobcatfish @afrittoli @tekton-robot