Description of problem:

The Operator/TektonConfig supports the field {{spec.pipeline.disable-affinity-assistant, }}however that field was removed upstream in Pipelines 1.0.0. It remains in the API for compatibility but has no effect on the Pipelines runtime. Users using this deprecated feature will still see the setting in their TektonConfig in 1.19.* but it will stop working.

Workaround

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

• Install Openshift Pipelines in a Cluster
• Edit the TektonConfig to enable the setting `pipeline.disable-affinity-assistant`

Actual results:

• The field existed, was set to its default value, and accepts the new value
• The setting has no effect

Expected results:

• The setting should not exist
• If a user tries to set the setting it should not be permitted as it does not exist
• Users upgrading from 1.18 to 1.19 who have this setting enabled should be notified that the setting no longer exists and we should follow any operator-upgrade best practices for such instances.

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

• The setting does not exist
• If a user tries to set the setting it is not be permitted
• Users upgrading from 1.18 to 1.19 who have this setting enabled receive the appropriate warnings or required action notifications

Definition of Done:

• Acceptance criteria is met
• Upstream docs are updated
• Downstream docs are updated or have been provided
• Release notes and upgrade documentation is provided

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *