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

synthetics-minion imagePullSecrets not inherited by runner pod spec #943

Open
keegoid-nr opened this issue Sep 10, 2022 · 0 comments
Open

Comments

@keegoid-nr
Copy link
Contributor

keegoid-nr commented Sep 10, 2022

Bug description

When setting an imagePullSecrets name, this works to pull the minion image from a private repository, but when the minion tries to pull the runner image from the same, it fails.

Version of Helm and Kubernetes

$ helm version --short
v3.9.4+gdbc6d8e
$ kubectl version --short
Client Version: v1.22.13
Server Version: v1.22.12-eks-6d3986b

Which chart?

1.0.51

What happened?

https://discuss.newrelic.com/t/synthetic-minion-runner-image/188741/5

What you expected to happen?

I would expect to see the following in the yaml output from a runner or healthcheck pod.

apiVersion: v1
items:
- apiVersion: v1
  kind: Pod
  spec:
    imagePullSecrets:
    - name: kmullaney312

How to reproduce it?

  1. host images in a private repository
  2. create a secret in your cluster
  3. configure values.yaml with your runner image repository, minion image, and imagePullSecrets.
  4. install with helm
helm upgrade --install synthetics-minion -n nr-minion newrelic/synthetics-minion -f values.yaml --create-namespace --version 1.0.51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants