Marcus Pritsch

Hello again, I had a hunch that maybe the image could not be pulled or analysed by trivy. I looked into the create jobs logs and used the command to...

Thank you for explaining your current implementation. You are saying that switching secrets to deterministic names would result in less secrets being creating. Hence we would only see a single...

Edit: So apparently I was not able to really disable polaris. I just removed our ImageReference, which somehow delayed the error messages. Not sure how that works but that explains...

I found the parameter to disable polaris and let it run for over an hour. So far no error logs regarding polaris and also no secrets being stuck. Alternatively I...

We now have a working version with polaris. The underlying issue were missing IAM permissions. We also needed to use polaris 4.2 instead of 5.0. Every starup of the starboard-operator...

Just a quick update. While we were able to fix the secret creation and errors on one cluster, another one keeps creating secrets. Not sure if this is a permission...

We have a bunch of clusters which get cluttered with old reports fairly fast. I honestly expected from the name `vulnerabilityScannerScanOnlyCurrentRevisions` that it would only keep new reports and remove...

Hey, thanks for the quick response. You are right, it is more important to identify what version we currently want to deploy, rather than the exact image-tag. Before going in...

Thanks for the quick response. I updated your tools and I tried to run "install-vortex.desktop" again, but this does not seem to fix it. Do you have any suggestions on...

Alright tried that just now: Now the "file validation" apparently gets done. Vortex still won't launch or log anything besides that: ``` Sat, 13 Jan 2024 21:43:22 GMT - info:...