Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

imagePullSecret becomes the image

See original GitHub issue


I’m not sure, but I think commit 1cae8dfe8b6485cf29c5699565ba557165b600b0 broke some things on Azure/k8s-deploy@v1. Basically the generated Kubernetes manifest seem to have wrong imagePullSecret value. Instead of the image pull secret, it’s the image value.

This is what I see in the deployed manifest in Kubernetes (the actual deployed).

  - name: '<retracted>'

This is where I expect imagePullSecret to contain sydnod-ci-container-registry and not<retracted>.

Creation of registery secret

Run Azure/k8s-create-secret@v1
/usr/bin/kubectl create secret docker-registry sydnod-ci-container-registry --docker-username *** --docker-password *** --docker-server *** --docker-email   -n sydnod-ci
secret/sydnod-ci-container-registry created

Deployment to Kubernetes

Run Azure/k8s-deploy@v1
    namespace: sydnod-ci
    manifests: ./manifests.yaml
    images: ***/sydnod-ci:web-dev-20200305-<retracted>
    imagepullsecrets: sydnod-ci-container-registry
    strategy: none
    traffic-split-method: pod
    baseline-and-canary-replicas: 0
    percentage: 0
    action: deploy

Hope anyone can shred some light on this issue.


Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

jeliassoncommented, Mar 5, 2020

@jeliasson I’ve rolled out the fix for my previous bug. Could you validate if you’re not broken?

It seems to be working again. My latest build went thru. If it’s not too much trouble, please have a staging branch or similar for v1.

thesattirajucommented, Mar 5, 2020

Closing this issue. I’ll take up the reverted fix separately.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Kubernetes imagePullSecrets not working; getting "image not ...
Another possible reason why you might see "image not found" is if the namespace of your secret doesn't match the namespace of the...
Read more >
Images - Kubernetes
Kubernetes supports specifying container image registry keys on a Pod. imagePullSecrets must all be in the same namespace as the Pod. The referenced...
Read more >
ImagePullSecrets | Running container image from Private ...
In this chapter, we look into how we can run an application where the application's container image is pushed into a private repository/registry....
Read more >
Kubernetes cluster-wide access to private container registry ...
Kubernetes allows us to configure private container registry credentials with imagePullSecrets on a per Pod or per Namespace basis.
Read more >
Cluster-wide registry authentication - Kubes&Clouds
Using private container image registries is a common practice in the ... own container runtime, this process can become way more complex.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found