Use kubectl api-resources for OLM check#131
Merged
Merged
Conversation
porridge
approved these changes
May 7, 2026
The kubectl api-resources command can fail for reasons other than OLM not being installed. Logging stderr and wrapping the error helps users diagnose the actual issue. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Instead of returning on the first missing resource, collect all missing ones and log each individually. The returned error gives a concise summary without duplicating the per-resource details. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Takes care of an important TODO: Use
kubectl api-resourcesto check if some APIs are actually usable.Prerequisite for CI rollout.
Manual verification
Deployed operator with
--olmwith roxie:Note that it detected OLM on the cluster. And also: