DFBUGS-3690:[release-4.16]: provider: do not send mon secret to client

[leelavg]

there is no requirement to send mon-secret to client and due to the change in content client.admin keyring is being overwritten at client end when both rook-op and client-op runs in same namespace.

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-3637](https://issues.redhat.com//browse/DFBUGS-3637), which is invalid:

• expected the bug to target the "odf-4.16.12" version, but no target version was set

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

Details

In response to this:

there is no requirement to send mon-secret to client and due to the change in content client.admin keyring is being overwritten at client end when both rook-op and client-op runs in same namespace.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[leelavg]

/hold
thinking to fix in 4.17 directly on client-op.

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-3690](https://issues.redhat.com//browse/DFBUGS-3690), which is invalid:

• expected the bug to target the "odf-4.16.12" version, but no target version was set

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

Details

In response to this:

there is no requirement to send mon-secret to client and due to the change in content client.admin keyring is being overwritten at client end when both rook-op and client-op runs in same namespace.

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.

[agarwal-mudit]

Closed because of red-hat-storage/ocs-client-operator#435

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-3690](https://issues.redhat.com//browse/DFBUGS-3690). The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

there is no requirement to send mon-secret to client and due to the change in content client.admin keyring is being overwritten at client end when both rook-op and client-op runs in same namespace.

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.