Closed aad closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/176260523
The labels on this github issue will be updated when the story is started.
Is your docker actually index.docker.io/my_dockerhub_account/...
? If so, that's fun 😄
For AKS, I saw an issue like this that seemed to require special authenticating the K8s cluster to your dockerhub to give it delete
access. The Azure documentation is here but with a brief search, I wasn't able to find a similar one for amazon/EKS.
it's not my real account name :)
Thanks for pointing out the direction. I have to test later, it's worth checking out since out account has with 6k images now. Please feel free close the ticket for now and i can update the comments if any findings.
Sounds good - thanks @aad!
Describe the bug
we are constantly receiving below errors when running cats (latest develop branch) against cf. The cf push is ok but we got timeout error in a few of test cases in cats, and we want to understand whether these are related.
Can you suggest how to check further?
I confirm the docker configs are present, from both rendered manifest and the registry-buddy env.
cf-api-worker > registry-buddy
Additional context
cf-for-k8s SHA
Please paste cf-for-k8s SHA hyperlink 1.0.0
Cluster information
Please provide IaaS name(s) here (GKE, AKS, EKS, minikube, kind, etc.) EKS with dockerhub as app registry
CLI versions
paste output of the following commands
ytt --version
:kapp --version
:kubectl version
:cf version
: cf version 7.1.0+4c3168f9a.2020-09-09