-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
gcp-auth addon now adds the image registry pull secret to newly created namespaces #15403
gcp-auth addon now adds the image registry pull secret to newly created namespaces #15403
Conversation
|
Welcome @iastewar! |
Hi @iastewar. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
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.
Could you run make generate-docs
to update the translations, thanks
/ok-to-test |
Would you mind adding a small test to our GCP-Auth tests that creates a new namespace and ensures the secret is there? |
kvm2 driver with docker runtime
Times for minikube start: 54.2s 55.1s 55.0s 55.0s 55.5s Times for minikube ingress: 28.7s 28.1s 25.2s 28.7s 28.7s docker driver with docker runtime
Times for minikube (PR 15403) start: 25.4s 24.5s 26.6s 27.0s 24.3s Times for minikube ingress: 22.0s 20.5s 21.0s 21.5s 20.0s docker driver with containerd runtime
Times for minikube start: 21.8s 21.8s 21.4s 33.9s 22.3s Times for minikube ingress: 26.0s 26.4s 26.4s 26.0s 26.5s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
Done |
kvm2 driver with docker runtime
Times for minikube ingress: 25.2s 26.2s 28.7s 27.6s 27.6s Times for minikube start: 54.2s 53.4s 52.6s 54.4s 54.3s docker driver with docker runtime |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
kvm2 driver with docker runtime
Times for minikube start: 53.6s 53.1s 53.5s 54.5s 52.6s Times for minikube ingress: 27.7s 27.1s 27.7s 28.1s 25.7s docker driver with docker runtime
Times for minikube start: 28.2s 25.4s 25.3s 26.2s 26.3s Times for minikube ingress: 23.0s 20.5s 22.0s 22.0s 19.5s docker driver with containerd runtime
Times for minikube start: 22.5s 23.3s 22.6s 21.8s 21.9s Times for minikube (PR 15403) ingress: 26.5s 26.0s 26.0s 26.0s 26.0s |
Seems like adding a timeout did not help unfortunately. Any other ideas why the test would be failing? Do you know if Jenkins is doing any image caching? |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
kvm2 driver with docker runtime
Times for minikube ingress: 22.7s 27.7s 28.1s 26.2s 28.2s Times for minikube start: 56.4s 55.3s 57.4s 54.7s 54.6s docker driver with docker runtime
Times for minikube ingress: 20.9s 21.0s 23.0s 21.0s 19.4s Times for minikube start: 24.9s 24.7s 25.2s 25.6s 25.0s docker driver with containerd runtime
Times for minikube (PR 15403) start: 25.0s 22.4s 25.2s 22.1s 21.9s Times for minikube ingress: 26.4s 57.4s 25.9s 26.0s 25.9s |
Looking at the webhook container logs, it seems that the token cannot be fetched due to an authorization problem so I'll look into this further. |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
So the problem was actually an obvious one: the credentials are invalid. They are pulled in from A few ideas:
Number 1 is the easiest and I am guessing we can't go with number 3. Thoughts? |
1 & 2 both seem fine, 3 likely not |
kvm2 driver with docker runtime
Times for minikube start: 54.5s 54.4s 51.8s 56.1s 52.8s Times for minikube ingress: 24.2s 25.2s 24.7s 29.1s 27.2s docker driver with docker runtime
Times for minikube ingress: 20.4s 21.5s 21.9s 21.0s 21.9s Times for minikube start: 25.6s 25.3s 25.8s 26.1s 26.1s docker driver with containerd runtime
Times for minikube start: 22.3s 22.3s 22.3s 22.6s 21.7s Times for minikube ingress: 26.4s 27.4s 27.5s 26.4s 26.5s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
…r from images map. This should be moved.
kvm2 driver with docker runtime
Times for minikube ingress: 27.7s 23.7s 23.6s 23.6s 27.7s Times for minikube start: 54.0s 54.8s 54.6s 53.4s 52.6s docker driver with docker runtime
Times for minikube start: 23.5s 25.5s 26.0s 26.6s 25.1s Times for minikube ingress: 21.5s 21.0s 22.5s 20.9s 21.0s docker driver with containerd runtime
Times for minikube ingress: 26.5s 27.4s 26.4s 26.5s 26.4s Times for minikube start: 21.9s 22.5s 21.5s 24.9s 25.3s |
kvm2 driver with docker runtime
Times for minikube (PR 15403) start: 55.3s 56.0s 54.2s 54.3s 55.8s Times for minikube ingress: 28.7s 28.6s 28.2s 29.1s 27.6s docker driver with docker runtime
Times for minikube start: 26.4s 25.4s 25.3s 24.9s 25.8s Times for minikube ingress: 19.9s 20.9s 21.5s 21.5s 49.4s docker driver with containerd runtime
Times for minikube ingress: 26.4s 26.4s 26.0s 26.4s 26.4s Times for minikube start: 21.5s 21.4s 21.8s 21.5s 21.6s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
kvm2 driver with docker runtime
Times for minikube ingress: 23.6s 24.1s 28.6s 25.6s 24.1s Times for minikube start: 51.1s 54.5s 53.7s 53.9s 52.7s docker driver with docker runtime
Times for minikube start: 28.3s 24.9s 28.0s 24.8s 25.3s Times for minikube (PR 15403) ingress: 19.9s 21.5s 20.9s 20.9s 21.0s docker driver with containerd runtime
Times for minikube ingress: 26.4s 26.5s 26.4s 26.4s 26.4s Times for minikube start: 20.6s 21.7s 32.4s 21.2s 20.7s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
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.
Looks good, thanks for the PR
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: iastewar, spowelljr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
fixes #13351
This should be merged after the webhook PR has been merged. Please see its description for more details.