-
Notifications
You must be signed in to change notification settings - Fork 5
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
Helm install fails due to failure to pull fortinet/fortiadc-ingress:2.0.2 image #13
Comments
The docker hub account was removed. On Dec 11, 2024, at 5:12 PM, Ian Halliday ***@***.***> wrote:
I have attempted to install the ingress controller helm chart using the instructions in the readme however the helm install fails. It times out:
% helm install fortiadc-ingress --namespace fortiadc-ingress --create-namespace --wait fortiadc-ingress-controller/fadc-k8s-ctrl
4:32PM
Error: INSTALLATION FAILED: context deadline exceeded
Looks like this is due to the pod failing to create because the container image cannot be found:
~ % kubectl describe pod -n fortiadc-ingress fortiadc-ingress-fadc-k8s-ctrl-bbf6f6c96-d65f8
Name: fortiadc-ingress-fadc-k8s-ctrl-bbf6f6c96-d65f8
... snip ...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m45s default-scheduler Successfully assigned fortiadc-ingress/fortiadc-ingress-fadc-k8s-ctrl-bbf6f6c96-d65f8 to cloudadmin-pool2-stcxq-mb4cp
Normal Pulling 74s (x4 over 2m44s) kubelet Pulling image "fortinet/fortiadc-ingress:2.0.2"
Warning Failed 74s (x4 over 2m44s) kubelet Failed to pull image "fortinet/fortiadc-ingress:2.0.2": failed to pull and unpack image "docker.io/fortinet/fortiadc-ingress:2.0.2": failed to resolve reference "docker.io/fortinet/fortiadc-ingress:2.0.2": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 74s (x4 over 2m44s) kubelet Error: ErrImagePull
Warning Failed 62s (x6 over 2m43s) kubelet Error: ImagePullBackOff
Normal BackOff 48s (x7 over 2m43s) kubelet Back-off pulling image "fortinet/fortiadc-ingress:2.0.2"
The fortinet user on dockerhub https://hub.docker.com/u/fortinet appears to have no images publicly available. Was it removed recently or is special permission required to pull the image?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi, |
It would seem that the whole fortinet dockerhub account is offline. On Dec 11, 2024, at 9:05 PM, lyanlin96 ***@***.***> wrote:
Hi,
Recently, the image for fortiadc ingress controller has been temporarily removed from dockerhub. We anticipate it will be available again within 1-2 weeks. Thank you.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
We reached out to Fortinet support, and they confirmed that the image should be back in 1-2 weeks. |
FYI they just updated us that there isn't an update yet from the Fortinet development team on this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have attempted to install the ingress controller helm chart using the instructions in the readme however the helm install fails. It times out:
Looks like this is due to the pod failing to create because the container image cannot be found:
The fortinet user on dockerhub https://hub.docker.com/u/fortinet appears to have no images publicly available. Was it removed recently or is special permission required to pull the image?
The text was updated successfully, but these errors were encountered: