Skip to content
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

Possibility to use custom imagePullSecret in scan jobs (marvin, popeye, trivy) #299

Open
recroutgr opened this issue Jun 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@recroutgr
Copy link

Feature Description

We want to have a possibility to inject imagePullSecrets values into scanning CroJob definitions (marvin, popeye and trivy). Currently, helm values for imagePullSecrets filed is injected only in Deployment for zora-operator.

Is your feature request related to a problem?

We want to use a private registry for all images related to the Zora project. For that we need to use imagePullSecrets. In values file of Zora helm chart we found a field responsible for that -

imagePullSecrets: []

But apparently it works only for zora-operator deployment, not for scan jobs (marvin, popeye, trivy). We also found out that CRD for clusterscan object (from which render of cronjob happens from my understanding - https://github.com/undistro/zora/blob/v0.8.4/charts/zora/crds/zora.undistro.io_plugins.yaml ) doesn't even have imagePullSecrets field, so it's not possible to add it there manually without editing the codebase.
Therefore, cluster cannot pull images from private registry to run scans and corresponding pods go into CrashLoopBackOff state.

What alternatives have you considered?

We haven't found any other way to inject imagePullSecret field into scan definition (CronJob/Job/Pod) without external interventions.
We came up with temporary solution: We use mutations inside Zora namespace to inject imagePullSecrets values into CronJobs definition. It works well but it's still a workaround.

@recroutgr recroutgr added the enhancement New feature or request label Jun 13, 2024
@matheusfm
Copy link
Contributor

Hi @recroutgr,
Thank you for your detailed feature request.
It makes sense and we understand the need for this enhancement.
We'll take a closer look into it. Contributions are always welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants