Ensure Twistlock logs to stdout
Per results of spike - https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/1123 - twistlock console/defenders don't seem to provide sufficient logging to stdout (minimal error logging sometimes).
Investigate this issue and if possible implement a fix to resolve. Depending on investigation of the issue there may be different outcomes of this issue:
- Could be an Ironbank image bug - if so, we would want to file a bug in the IB repo(s) and track that through resolution
- Could be values/manifest pieces missing from our chart - if so we would want to fix those and include the fix in a new twistlock tag
- Could be just a limitation of upstream logging, i.e. the application just has poor logging and there are no ways we can improve it on our end (since Twistlock/Prisma Cloud Compute is closed source). If this is the case we'd like to get this feedback back to PA, so reach back out to the team to find a way to contact them with feedback.
Edited by Micah Nagel