Closed eguzki closed 1 month ago
:warning: Please install the to ensure uploads and comments are reliably processed by Codecov.
Attention: Patch coverage is 77.41935%
with 7 lines
in your changes missing coverage. Please review.
Project coverage is 83.94%. Comparing base (
de60fb3
) to head (347991e
).
Files with missing lines | Patch % | Lines |
---|---|---|
pkg/reconcilers/deployment.go | 44.44% | 5 Missing :warning: |
controllers/limitador_controller.go | 84.61% | 2 Missing :warning: |
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