SRVKP-5832: maintain pinning of watcher image to mem leak version

[gabemontero]

Until @khrm can either productize his third party tool integration for results log storage, or unless the backup option of accessing S3 from the watcher is done at a tactical solution, the current mem leak version of the watcher still provides slightly better success / performance than the versions that fix the mem leak / cancelled context issues but are more negatively impacted by grpc/http2 scaling issues.

I did run generate-deploy-config.sh @enarha in both the staging and production folders.

rh-pre-commit.version: 2.3.0
rh-pre-commit.check-secrets: ENABLED

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: gabemontero

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:

• components/pipeline-service/OWNERS

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: gabemontero

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:

• components/pipeline-service/OWNERS

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

[openshift-ci]

@gabemontero: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/appstudio-hac-e2e-tests	c41c3b4	link	false	/test appstudio-hac-e2e-tests

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.

[enarha]

This line has to be reverted manually until we switch that line https://github.com/redhat-appstudio/infra-deployments/blob/main/components/pipeline-service/production/base/kustomization.yaml#L11 to match the one in staging which points to a pipeline-service SHA including the fix.
The same goes for all production deploy.yaml files.

[gabemontero]

@enarha PR rebased now that July 16 prod bump has gone through - PTAL / thanks

[enarha]

@enarha PR rebased now that July 16 prod bump has gone through - PTAL / thanks

That is not enough because the prod update did not include the newest SHA from the pipeline-service repo, but took only 2 commits including the OSP bump. You need to update https://github.com/redhat-appstudio/infra-deployments/blob/main/components/pipeline-service/production/base/kustomization.yaml#L11 to da64420f8df634736b1aff727155e626ec832dd1 if you want to include the fixes.

[gabemontero]

@enarha PR rebased now that July 16 prod bump has gone through - PTAL / thanks

That is not enough because the prod update did not include the newest SHA from the pipeline-service repo, but took only 2 commits including the OSP bump. You need to update https://github.com/redhat-appstudio/infra-deployments/blob/main/components/pipeline-service/production/base/kustomization.yaml#L11 to da64420f8df634736b1aff727155e626ec832dd1 if you want to include the fixes.

thanks updated @enarha

[enarha]

/lgtm