pingcap / pingcap/docs-tidb-operator
部署 TiDB 集群监控 UCloud 上的镜像不存在
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 129
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
File: /release-1.3/zh/get-started.md
# typo:
kubectl -n tidb-cluster apply -f https://raw.githubusercontent.com/pingcap/tidb-operator/master/examples/basic-cn/tidb-monitor.yaml
# log
Normal Scheduled 5m5s default-scheduler Successfully assigned tidb-cluster/basic-monitor-0 to kind-worker
Normal Pulling 3m33s (x4 over 5m5s) kubelet Pulling image "uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1"
Warning Failed 3m33s (x4 over 5m5s) kubelet Failed to pull image "uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1": rpc error: code = NotFound desc = failed to pull and unpack image "uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1": failed to resolve reference "uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1": uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1: not found
Warning Failed 3m33s (x4 over 5m5s) kubelet Error: ErrImagePull
Warning Failed 3m21s (x6 over 5m5s) kubelet Error: ImagePullBackOff
Normal BackOff 3m10s (x7 over 5m5s) kubelet Back-off pulling image "uhub.service.ucloud.cn/pingcap/tidb-monitor-initializer:v5.4.1"
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 release-1.3/zh/get-started.md and inspect the tidb-monitor.yaml command it links to. Verify the referenced tidb-monitor-initializer:v5.4.1 image and update the documentation to a valid deployment reference; done means the documented command no longer requests the missing image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100