Skip to content

[enterprise-4.11] Issue in file operators/understanding/olm-understanding-operatorhub.adoc #51076

@flozanorht

Description

@flozanorht

Which section(s) is the issue in?

Example OperatorHub custom resource

What needs fixing?

Listing "Example OperatorHub custom resource" makes no sense. If I already disabled "All default catalog sources" why would I also disable the "community operators" catalog source? It might me valid syntax for the custom resource but a confusing example with unclear purpose.

Such example could make sense if instead of naming one of the default catalog sources, it named a custom catalog source and also provided some context on the custom catalog sources configured on the target cluster. Or maybe it should be split into two distinct examples: one of how to disable all default catalog sources, and another on how to selective disable some of the default catalog sources while leaving others enabled.

Whatever the solution, such examples require some "before/after" listings to show the initial state of the cluster, before applying the custom resource, and after applying.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions