Daniel Pacak

Hi @avdhoot ! Thank you for reporting this issue. I'm going to follow up on that and link it to a parent story or epic about configuring scanners. In your...

@avdhoot Actually starboard can use image pull secret attached to the Pod template or the service account. In your case did you set the secret on the Pod template level...

Thank you for providing all the details @avdhoot So just to rephrase and confirm my understanding: You neither use image pull Secret set at Pod template not Service Account. You're...

@avdhoot I renamed the title of this issue to reflect the specific use case of kops and authorizing Kubernetes nodes to pull images from private registry and repositories. As already...

> @danielpacak > > I am trying to make use of the above discussed functionality within AKS. I am not finding that the operator pulls the imagePullSecret of the deployment....

Hi @mathieudebrito Starboard CLI and Starboard Operator v0.9 should read image pull Secret from pod template as explained [here](https://aquasecurity.github.io/starboard/latest/integrations/private-registries/). If that's not the case it may be regression. I'll double...

Hey @mathieudebrito I can reproduce this error so it seems to be regression or a corner case that's not handled properly by Starboard (both operator and CLI as they share...

I found what was causing this problem. Essentially you can create image pull secret which is actually concatenation of registry server (`rg.pl-waw.scw.cloud`) and repository name (`private`). If that was the...

> Hi, any chance to add supporting the private registry to the Helm, please? > I'm getting this error: > `unable to initialize a scanner: unable to initialize a docker...

👋 @ryanbrainard I think we have already mentioned somewhere that mounting container runtime sockets is suboptimal for these reasons: - Starboard must figure out the Container Runtime used on each...