Add LimitRange Examples for PipelineRun and TaskRun

[danielhelfand]

Adding some examples to illustrate #1991 for specifying a LimitRangeName as part of pipelineruns/taskruns.

Submitter Checklist

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

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

Release Notes

Add examples for specifying a LimitRangeName as part of a pipelinerun/taskrun

[danielhelfand]

/test pull-tekton-pipeline-integration-tests

[ghost]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbwsg

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:

• OWNERS [sbwsg]

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

[danielhelfand]

/test pull-tekton-pipeline-integration-tests

[danielhelfand]

Unfortunately, the examples here create a LimitRange which causes all other examples to fail since they don't take into account limitRangeName. Moving the examples to no-ci and will make them more visible by including in documentation.

[ghost]

oh cool, i didn't know no-ci existed!

Would be great to get these limitranges running on every push at some point though. I'll create an issue on plumbing to address this - maybe we need to run each example in its own namespace?

/lgtm

[danielhelfand]

• maybe we need to run each example in its own namespace?

Yeah, if these examples are excluded from the others in a different namespace, they would work. But would be great if we could create different namespaces for certain examples.