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

Store kube-forensics-worker image in private registry #26

Open
robbo10 opened this issue Jan 5, 2021 · 0 comments
Open

Store kube-forensics-worker image in private registry #26

robbo10 opened this issue Jan 5, 2021 · 0 comments

Comments

@robbo10
Copy link

robbo10 commented Jan 5, 2021

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:

Once you submit the podcheckpoint the forensics-controller-manager pod then spins up the job.batch/podcheckpoint, which in turn starts the pod/podcheckpoint.  This is currently coming from keikoproj/kube-forensics-worker

What you expected to happen:
We would like the keikoproj/kube-forensics-worker image to come from an internal registry to meet our security requirements.

How to reproduce it (as minimally and precisely as possible):
Submit the podcheckpoint

Anything else we need to know?:

Environment:

  • kube-forensics version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

  • PodCheckpoint status:
$ kubectl describe -n forensics-system podcheckpoint <checkpoint-name>
  • controller logs:
$ kubectl logs -n forensics-system <forensics-controller-manager pod>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant