Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set infrawatch-operators to highest priority #512

Closed
wants to merge 1 commit into from

Conversation

leifmadsen
Copy link
Member

Set the priority to -200 to make the infrawatch-operators CatalogSource
a higher priority than redhat-operators CatalogSource.

Setting the priority to highest values means the dependency resolution
will resolve Smart Gateway Operator (SGO) out of the
infrawatch-operators CatalogSource instead of from the redhat-operators
CatalogSource, which could result in failed deployments if there are
changes in SGO required within Service Telemetry Operator.

Set the priority to -200 to make the infrawatch-operators CatalogSource
a higher priority than redhat-operators CatalogSource.

Setting the priority to highest values means the dependency resolution
will resolve Smart Gateway Operator (SGO) out of the
infrawatch-operators CatalogSource instead of from the redhat-operators
CatalogSource, which could result in failed deployments if there are
changes in SGO required within Service Telemetry Operator.
@leifmadsen leifmadsen requested review from csibbitt and vkmc November 22, 2023 14:44
@leifmadsen
Copy link
Member Author

I misremembered thinking the community operators were positive numbers, but they are not. The community-operators CatalogSource is at -400 which is a lower priority than the redhat-operators CatalogSource priority of -100. By default, priority is set to a value of zero, meaning infrawatch-operators is already at the highest priority. I am closing this as unnecessary.

@leifmadsen leifmadsen closed this Nov 22, 2023
@leifmadsen leifmadsen deleted the lmadsen/infrawatch-highest-priority branch November 22, 2023 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant