search

cloudfoundry / capi-k8s-release

The CF API parts of cloudfoundry/cf-for-k8s
Apache License 2.0
9 stars 25 forks source link

container registry-buddy in cf-api-server and cf-api-worker pods always stop #117

Open davincizhao opened 3 years ago

davincizhao commented 3 years ago

registry-buddy in cf-api-server and cf-api-worker pods always stop and start

sometime is works, sometime in crash status. restart again and again.

cf-gitbot commented 3 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/179227864

The labels on this github issue will be updated when the story is started.

davincizhao commented 3 years ago

Server is listening at 127.0.0.1:8080... 2021/08/15 04:19:24 Server is attempting to shut down... 2021/08/15 04:19:27 Server stopped image

davincizhao commented 3 years ago

image

nicko170 commented 2 years ago

@davincizhao I was seeing the same thing. I have fixed it by introducing a longer timeout, as the health check fails when dockerhub is more than 1 second away, each call to the endpoint results in an external call to docker and the default 1 second timeout just wasn't cutting it.

This does mean you will have to edit the cf-for-k8s local files too. I'd suggest forking this repo, making the same changes I did in #120, and using your own URL and commit ref instead of mine, whilst we wait for @cloudfoundary to merge.

in cf-for-k8s/vendir.yml - update where the capi-k8s-release comes from

directories:
- path: config/capi/_ytt_lib/capi-k8s-release
  contents:
  - path: .
    git:
      url: https://github.com/nicko170/capi-k8s-release
      ref: 2e9979e78ae6f2a640db8a6132b0c56fe8676119

run vendir sync to pull the changes Regenerate your rendered file ytt -f config -f ${TMP_DIR}/cf-values.yml > ${TMP_DIR}/cf-for-k8s-rendered.yml

And finally, kapps deploy will work. kapp deploy -a cf -f ${TMP_DIR}/cf-for-k8s-rendered.yml -y

bosh-admin-bot commented 2 years ago

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

p-bizouard commented 2 years ago

We had exactly the same problem here, on a k8s in France (managed by OVHCloud). The PR https://github.com/cloudfoundry/capi-k8s-release/pull/120 resolved the issue.

Ty @nicko170 👍