external: dont call telemetry if the cluster is external

[parth-gr]

closes: rook#11470
Signed-off-by: parth-gr paarora@redhat.com
(cherry picked from commit a52e2f1)

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide).
• Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

[openshift-ci]

@parth-gr: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

external: dont call telemetry if the cluster is external

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: parth-gr
Once this PR has been reviewed and has the lgtm label, please assign obnoxxx for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[travisn]

@parth-gr Is there a BZ for this backport?

[parth-gr]

@parth-gr Is there a BZ for this backport?

No @travisn Is this something good to have it,
For the 4.13 code it got auto committed by the branch,

Is a BZ needed so?

[travisn]

For any downstream backport we need a BZ that is approved by PM/QE for merge. In this case, since the errors will just be seen in the operator log and can be ignored, customer impact is low so I don't think a backport is needed.

[parth-gr]

Okay thanks for the feedback, closing