Docker Rancher Upgrade to 2.11.1 (from v2.6.8 -> 2.10.3 -> 2.11.1)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 30
- Forks
- 87
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 93
Description
Received the following errors on trying to upgrade to docker image 2.11.1
2025/05/09 03:23:43 [ERROR] RDPClient: error reading connect secret: secrets "api-extension" not found, will attempt to create new one...
2025/05/09 03:23:43 [ERROR] RDPClient: error creating connect secret: Internal error occurred: failed calling webhook "rancher.cattle.io.secrets": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation/secrets?timeout=15s": no endpoints available for service "rancher-webhook"
2025/05/09 03:23:43 [FATAL] Internal error occurred: failed calling webhook "rancher.cattle.io.secrets": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation/secrets?timeout=15s": no endpoints available for service "rancher-webhook"
Followed this guide: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/upgrade-docker-installed-rancher
Tested removal of the rancher webhook before attempting the upgrade to 2.11.1, and it worked on the test docker container. However, I am unsure if this will cause any issues that I am currently unaware of.
Is there any other way of resolving this error?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked single-node Docker upgrade guide and the reported failure at the rancher-webhook service endpoint during the 2.11.1 upgrade. Compare the test-container result after removing rancher-webhook with the failing upgrade path, and establish a documented, upgrade-safe resolution without leaving webhook behavior ambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100