OCPBUGS-35217: Fix incorrect example in Release Notes

[simonkrenger]

The field originally described does not work as expected. This commit adds the missing data field in the example.

Version(s): pipelines-docs-1.14

Issue: https://issues.redhat.com/browse/OCPBUGS-35217

Link to docs preview: -

QE review:

• QE has approved this change.

Additional information:

In the Release notes for Red Hat OpenShift Pipelines General Availability 1.14 there is the following section (https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#new-features-1-14_op-release-notes):

With this update, you can define default resource requirements for containers and init-containers in pods that OpenShift Pipelines creates when executing task runs. Use the pipeline.options.configMaps.config-defaults.default-container-resource-requirements spec in the TektonConfig CR to set these requirements. You can set the default values for all containers and also for particular containers by name or by prefix, such as sidecar-*.

However the field described does not work as expected. When trying to use oc patch to add content to such a field the user will get an error like this:

Error from server (BadRequest): admission webhook "webhook.operator.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "default-container-resource-requirements"

This commit fixes that issue.

[openshift-ci-robot]

@simonkrenger: This pull request references Jira Issue OCPBUGS-35217, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected Jira Issue OCPBUGS-35217 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

The field originally described does not work as expected. This commit adds the missing data field in the example.

Version(s): OpenShift Pipelines 1.14

Issue: https://issues.redhat.com/browse/OCPBUGS-35217

Link to docs preview: -

QE review:

• QE has approved this change.

Additional information:

In the Release notes for Red Hat OpenShift Pipelines General Availability 1.14 there is the following section (https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#new-features-1-14_op-release-notes):

With this update, you can define default resource requirements for containers and init-containers in pods that OpenShift Pipelines creates when executing task runs. Use the pipeline.options.configMaps.config-defaults.default-container-resource-requirements spec in the TektonConfig CR to set these requirements. You can set the default values for all containers and also for particular containers by name or by prefix, such as sidecar-*.

However the field described does not work as expected. When trying to use oc patch to add content to such a field the user will get an error like this:

Error from server (BadRequest): admission webhook "webhook.operator.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "default-container-resource-requirements"

This commit fixes that issue.

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 openshift-eng/jira-lifecycle-plugin repository.

[ocpdocs-previewbot]

🤖 Fri Jun 21 13:59:18 - Prow CI generated the docs preview:

https://77867--ocpdocs-pr.netlify.app/openshift-pipelines/latest/about/op-release-notes.html

[openshift-ci]

@simonkrenger: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[simonkrenger]

PTAL @mramendi

[simonkrenger]

PTAL @mramendi Thanks

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mramendi]

lgtm

[mramendi]

lgtm - please reach me on slack with such issues as I failed to notice. Also please change the "version" to "pipelines-docs-1.14" as it needs to be merged there.

[mramendi]

/label peer-review-done

[openshift-ci-robot]

@simonkrenger: This pull request references Jira Issue OCPBUGS-35217, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-35217 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

The field originally described does not work as expected. This commit adds the missing data field in the example.

Version(s): pipelines-docs-1.14

Issue: https://issues.redhat.com/browse/OCPBUGS-35217

Link to docs preview: -

QE review:

• QE has approved this change.

Additional information:

In the Release notes for Red Hat OpenShift Pipelines General Availability 1.14 there is the following section (https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#new-features-1-14_op-release-notes):

With this update, you can define default resource requirements for containers and init-containers in pods that OpenShift Pipelines creates when executing task runs. Use the pipeline.options.configMaps.config-defaults.default-container-resource-requirements spec in the TektonConfig CR to set these requirements. You can set the default values for all containers and also for particular containers by name or by prefix, such as sidecar-*.

However the field described does not work as expected. When trying to use oc patch to add content to such a field the user will get an error like this:

Error from server (BadRequest): admission webhook "webhook.operator.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "default-container-resource-requirements"

This commit fixes that issue.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@simonkrenger: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

The field originally described does not work as expected. This commit adds the missing data field in the example.

Version(s): pipelines-docs-1.14

Issue: https://issues.redhat.com/browse/OCPBUGS-35217

Link to docs preview: -

QE review:

• QE has approved this change.

Additional information:

In the Release notes for Red Hat OpenShift Pipelines General Availability 1.14 there is the following section (https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#new-features-1-14_op-release-notes):

With this update, you can define default resource requirements for containers and init-containers in pods that OpenShift Pipelines creates when executing task runs. Use the pipeline.options.configMaps.config-defaults.default-container-resource-requirements spec in the TektonConfig CR to set these requirements. You can set the default values for all containers and also for particular containers by name or by prefix, such as sidecar-*.

However the field described does not work as expected. When trying to use oc patch to add content to such a field the user will get an error like this:

Error from server (BadRequest): admission webhook "webhook.operator.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "default-container-resource-requirements"

This commit fixes that issue.

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 openshift-eng/jira-lifecycle-plugin repository.

[kalexand-rh]

/remove-lifecycle stale

[openshift-ci-robot]

@simonkrenger: This pull request references Jira Issue OCPBUGS-35217, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-35217 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

The field originally described does not work as expected. This commit adds the missing data field in the example.

Version(s): pipelines-docs-1.14

Issue: https://issues.redhat.com/browse/OCPBUGS-35217

Link to docs preview: -

QE review:

• QE has approved this change.

Additional information:

In the Release notes for Red Hat OpenShift Pipelines General Availability 1.14 there is the following section (https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#new-features-1-14_op-release-notes):

With this update, you can define default resource requirements for containers and init-containers in pods that OpenShift Pipelines creates when executing task runs. Use the pipeline.options.configMaps.config-defaults.default-container-resource-requirements spec in the TektonConfig CR to set these requirements. You can set the default values for all containers and also for particular containers by name or by prefix, such as sidecar-*.

However the field described does not work as expected. When trying to use oc patch to add content to such a field the user will get an error like this:

Error from server (BadRequest): admission webhook "webhook.operator.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "default-container-resource-requirements"

This commit fixes that issue.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale