-
Notifications
You must be signed in to change notification settings - Fork 89
falcon-image-analyzer pod produces error logs. #338
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
Comments
Hey @Blizter -- you have Also note that only the latest release of this chart supports Apologies for the confusion as I see some other charts do use |
@Blizter Were you able to get this working? |
@evanstoner do we have any option to log only error log not info logs in IAR pod? |
@cs-pvyas see question above
|
@hh-madhuprasad not today, but I passed your request on to engineering. I'm going to close this issue since the OP has not responded in a while. |
Hello,
I am currently working on setting the image analyzer on our Infra, however I am facing a situation where we are able to pull the image from our private registry (after pull from CS then retagging). When deploying the image analyzer using the helm charts I get the following log in the falcon-image-analyzer :
here is the content of the values.yaml provided to the helm charts :
Are we missing something?
I have been scratching my head since Monday, We checked several time the client id/secret scopes, the configs the doc, etc.
I saw CrowdStrike/falcon-operator#571 and wondering if something is missing on the doc side that is creating this situation
Thank you for your help.
The text was updated successfully, but these errors were encountered: