Adding the Kraken-scenario task into catalog

[startxfr]

Changes

• Add kraken scenario task to use a chaos scenarios task in pipelines

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you review them:

• [x] Follows the authoring recommendations
• [x] Includes docs (if user facing)
• [x] Includes tests (if functionality of task changed or new task added)
• [x] Commit messages follow commit message best practices
• [x] Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation
  • [x] File path follows <kind>/<name>/<version>/name.yaml
  • [x] Has README.md at <kind>/<name>/<version>/README.md
  • [x] Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource
  • [x] Has mandatory metadata.annotations tekton.dev/pipelines.minVersion
  • [x] mandatory spec.description follows the convention

---

[tekton-robot]

Hi @startxfr. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[startxfr]

split PR https://github.com/tektoncd/catalog/pull/999

[startxfr]

@vdemeester i've followed your advices and split each task into it's own commit and this one is for kraken scenario chaos testing task. @vinamra28 do you need anything else to validate this PR ? Do you think it's valuable to the community ?

[startxfr]

@vinamra28 @vdemeester : I still see a 'do-not-merge/invalid-owners-file'. I've done the easyCLA and tekton org addition. Is there anything else i need to do validate the ownership of the files ?

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
ERROR: Step "" uses image "quay.io/chaos-kubox/krkn:latest" which must be tagged with a specific version
WARN : Step "" uses secret as environment variables. Prefer using secrets as files over secrets as environment variables

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign dlorenc after the PR has been reviewed. You can assign the PR to them by writing /assign @dlorenc in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[tekton-robot]

Catlin Output

FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
WARN : Step "" uses image "$(params.image)" that contains variables; skipping validation

[tekton-robot]

Catlin Output

FILE: task/git-clone/0.7/git-clone.yaml
WARN : Step "clone" uses image "$(params.gitInitImage)" that contains variables; skipping validation
FILE: task/kraken-scenario/0.1/kraken-scenario.yaml
WARN : Step "" uses image "$(params.image)" that contains variables; skipping validation

[tekton-robot]

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.

[vinamra28]

/remove-lifecycle stale

[startxfr]

do i need to do something ?

[tekton-robot]

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.

[tekton-robot]

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.

[tekton-robot]

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]

@tekton-robot: Closed this PR.

In response to this:

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.

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.