Bug 1917799: Gather list of OLM operator names and versions & minor clean up

[tremes]

This PR gathers all the names & versions of the installed OLM operators using dynamic client & some clean up.

I am still wondering what the relation between ClusterServiceVersion and Operator kind is and why the versions (v1alpha1 and v1) are different when both are from operators.coreos.com. The sets of these kinds are not equal that's why I implemented with using Operator, but it would be much more straightforward using ClusterServiceVersion.

Categories

• Bugfix
• Enhancement
• Backporting
• Others (CI, Infrastructure, Documentation)

Sample archive

• docs/insights-archive-sample/config/olm_operators.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gather/clusterconfig/olm_operators_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Not yet

References

https://issues.redhat.com/browse/???
https://bugzilla.redhat.com/show_bug.cgi?id=???
https://access.redhat.com/solutions/???

[tremes]

/test insights-operator-e2e-tests

[openshift-ci-robot]

@tremes: This pull request references Bugzilla bug 1917799, 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.7.0) matches configured target release for branch (4.7.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1917799: Gather list of OLM operator names and versions & minor clean up

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.

[tremes]

/retest

[tremes]

/retest

[0sewa0]

Tested it with cluster-bot.

• Installed 2 OLM operators using the web UI
• Applied the 03-clusterrole.yaml
• Got output [{"name":"awx-resource-operator.openshift-operator-lifecycle-manager","version":"v0.1.0"},{"name":"kiali-ossm.openshift-operators","version":"v1.24.4"}]

/lgtm

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[0sewa0]

tested it again, same as before (but only installed 1 OLM operator)
Got output: [{"name":"awx-resource-operator.default","version":"v0.1.0"}]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0sewa0, tremes

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:

• OWNERS [0sewa0,tremes]

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

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci-robot]

@tremes: All pull requests linked via external trackers have merged:

• openshift/insights-operator#316

Bugzilla bug 1917799 has been moved to the MODIFIED state.

In response to this:

Bug 1917799: Gather list of OLM operator names and versions & minor clean up

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.