kubernetes-sigs / alibaba-cloud-csi-driver

CSI Plugin for Kubernetes, Support Alibaba Cloud EBS/NAS/OSS/CPFS
Apache License 2.0
540 stars 241 forks source link

自建k8s无法使用OSS插件 #736

Closed helloxubo closed 10 months ago

helloxubo commented 1 year ago

自建的K8S在使用的OSS时日志中提示:“Failed connect to 100.100.100.200:80; Connection timed out”。 经排查,IP”100.100.100.200“”只有阿里云的服务器才能连接。其它的服务器无法访问。 可有其它的解决办法,谢谢?

cuericlee commented 1 year ago

Pls leverage register cluster to install latest CSI from addon center for self-build K8s cluster. https://help.aliyun.com/document_detail/335175.html

zhangzhenhuajack commented 1 year ago

第一步:参考文档:https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/blob/v1.1.6/docs/oss.md 安装oss-csi-plugin 插件;

1)从这个文档中可以知道 kubectl create -f ./deploy/oss/oss-plugin.yaml 进行发布,但是发不完之后,观察 kubectl -n kube-system logs -f csi-plugin-jpw6n -c csi-plugin 报“Failed connect to 100.100.100.200:80; Connection timed out”。 错误,并且有一些centos的命令操作,所以猜想可能镜像不对。

2)通过上面的文档$ cd build && sh build-oss.sh 也知道了如何编译源码,于是乎查看 Dockfile和entrypoint.sh 根据node的操作系统的版本做了如下修改: image image image image image

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

majiajun7 commented 1 year ago

+1 我也遇到此问题

AlbeeSo commented 1 year ago

+1 我也遇到此问题

@majiajun7 方便问问现在您使用的CSI版本吗?确认一下是否已经带上该bugfix: https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/pull/825/files

k8s-triage-robot commented 10 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 10 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/issues/736#issuecomment-1902056391): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.