Add a check command

[ghost]

Version and Operating System

All supported versions and operating systems.

Expected Behavior

tkn provides a check subcommand that will look at your currently configured cluster and ensure the following:

1. k8s is reachable
2. the k8s version is compatible
3. tekton's controller and webhook is up and running
4. any configured sibling projects (e.g. triggers) are up and running
5. (Maybe?) run a very simple dummy pipeline as a smoke test

A failure at any step could result in some clear notice being written to the screen to tell the user which

This feature was suggested by @bobcatfish after working with LinkedD's check command: https://linkerd.io/2/reference/cli/check/

[ghost]

/label feature

[ghost]

/add-label feature

[chmouel]

/kind feature

[chmouel]

I like it !!

thanks to @waveywaves I think we have the version on the server now and that should not be difficult to implement.

The thing I think we should probably think about :

• Define and formalize compatibility i.e: (current-2)
• if controller and webhook is running, do we care about multiple tekton versions? (I guess not cause that's not really supported?)
• We need emojis on each check test output 😋

[tekton-robot]

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]

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]

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