OBSDOCS-1371: Add a release note about change of parameter name from 'delivery' to 'deliveryMode'

[max-cx]

Version(s): 4.14, 4.15, 4.16, 4.17, 4.18

Issue: https://issues.redhat.com/browse/OBSDOCS-1371

Link to docs preview: https://86601--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.0/log6x-release-notes.html#log6x-release-notes-6-0-0-enhancements

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1371 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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]

@max-cx: This pull request references OBSDOCS-1371 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

Version(s): 4.14, 4.15, 4.16, 4.17, 4.18

Issue: https://issues.redhat.com/browse/OBSDOCS-1371

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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]

🤖 Mon Jan 06 11:02:10 - Prow CI generated the docs preview:

https://86601--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.0/log6x-release-notes.html

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1371 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

Version(s): 4.14, 4.15, 4.16, 4.17, 4.18

Issue: https://issues.redhat.com/browse/OBSDOCS-1371

Link to docs preview: https://86601--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.0/log6x-release-notes.html#log6x-release-notes-6-0-0-enhancements

QE review:

• QE has approved this change.

Additional information:

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.

[max-cx]

/label peer-review-needed

[jeana-redhat]

LGTM
/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done

[openshift-ci-robot]

@max-cx: This pull request references OBSDOCS-1371 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

Version(s): 4.14, 4.15, 4.16, 4.17, 4.18

Issue: https://issues.redhat.com/browse/OBSDOCS-1371

Link to docs preview: https://86601--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.0/log6x-release-notes.html#log6x-release-notes-6-0-0-enhancements

QE review:

• QE has approved this change.

Additional information:

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]

@max-cx: 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.

[max-cx]

/label merge-review-needed

[mburke5678]

@max-cx Is it just the one parameter that was changed, or only one that the end user needs to be concerned with?

This enhancement updates the ClusterLogForwarder API to follow the Kubernetes standards.

This makes it sound like there were multiple API changes, but we only show a few parameters (and assume folks know which ones were changed).