-
Notifications
You must be signed in to change notification settings - Fork 14
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
pull an image from a private registry #160
pull an image from a private registry #160
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #160 +/- ##
==========================================
- Coverage 84.90% 83.94% -0.97%
==========================================
Files 19 19
Lines 994 1009 +15
==========================================
+ Hits 844 847 +3
- Misses 97 106 +9
- Partials 53 56 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
eb2e95c
to
2cdb660
Compare
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
2cdb660
to
71778b2
Compare
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
71778b2
to
42236a8
Compare
Signed-off-by: Eguzki Astiz Lezaun <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified! Changes looks good to me! 👍
What
Pull an image from a private registry
Fixes #78
Verification steps
First, get some limitador image on a private repository. For example:
quay.io/eastizle/limitador-private:v1.6.0
(this repo and image will be removed when this PR is merged).dev setup
Create a Secret of type `kubernetes.io/dockerconfigjson by providing credentials. For example, using kubectl tool with the following command line:
Deploy limitador with a custom image and a reference to the recently created
regcred
secret.Wait for limitador to be ready
Check status
It should say
Ready
.Now, let's deploy limitador with custom image from a private repository without providing imagepullsecrets. It will be a custom image different from the one used in the previous example. As the image of the previous example is already present in the cluster and the limitador deployment pullpolicy is "IfNotPresent", using that image even without imagepullsecrets would not fail.
Check status
The answer should be: not "ready" with somewhat confusing message: "Deployment does not have minimum availability"
Checking pod status or events we can get more detailed information:
You should see
https://quay.io/v2/eastizle/limitador-private/manifests/other: 401 UNAUTHORIZED
Cleanup