Hint at OpenShift pull secret needed for IAR. #597
Merged
Conversation
This file contains 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.
Discussed and confirmed internally by TSE and Consulting, providing the OpenShift cluster pull secret is required for IAR to scan cluster control plane resources that come from Red Hat registries. Since we know this is the case, just specify it in the docs. (This is easier and more private than opting customers in automatically e.g. by the operator detecting the cluster is OpenShift and injecting the secret reference without an explicit opt-in.)
I could wrap the guidance in
{{- if eq .Distro "openshift" }}but figured it was safer to have the update in the generic resources docs as well, in case someone is not looking at the OpenShift-specific resources.