Bug 1834852: Add make target to run operator with telepresence

[marun]

NOTE openshift/build-machinery-go#14 needs to merge before this PR.

Once telepresence has been installed (see the run-telepresence.sh script for instructions), make telepresence will replace the operator's pod with a local process that has access to the same environment as the pod. This can speed up development since iteration doesn't require cycles of image build/push/pull. See https://telepresence.io for more details.

[openshift-ci-robot]

@marun: This pull request references Bugzilla bug 1834852, which is invalid:

• expected the bug to target the "4.5.0" release, but it targets "---" instead

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

Details

In response to this:

Bug 1834852: Add make target to run operator with telepresence

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/test-infra repository.

[marun]

/bugzilla refresh

[openshift-ci-robot]

@marun: This pull request references Bugzilla bug 1834852, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.5.0) matches configured target release for branch (4.5.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Details

In response to this:

/bugzilla refresh

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/test-infra repository.

[stlaz]

I assume this might be related to my custom setup, but it would appear that when the cluster-deployed operator tries to connect together with the local telepresence client, this never really happens.

I can see the local telepresence instance asking me for password to SSH to telepresence@127.0.0.1, but the prompt is not really interactive as the script isn't, and I can see the remote pod logging its failed attempts:

2020-05-13T12:53:26+0000 [Poll#error] Failed to contact Telepresence client:
2020-05-13T12:53:26+0000 [Poll#error] Connection was refused by other side: 111: Connection refused.
2020-05-13T12:53:26+0000 [Poll#warn] Perhaps it's time to exit?

[stlaz]

/lgtm

Turns out I was using a wrong telepresence version (kudos to @marun), this works well 👍

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marun, stlaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [stlaz]

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

[openshift-ci-robot]

@marun: Some pull requests linked via external trackers have merged: openshift/cluster-authentication-operator#276. The following pull requests linked via external trackers have not merged:

• openshift/cluster-etcd-operator#321 is open
  Bugzilla bug 1834852 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1834852: Add make target to run operator with telepresence

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/test-infra repository.