我有几个pages,我发现了类似的问题和大多数答案告诉我们白名单我们的IP。但是,我允许从地图集中的任何地方访问0.0.0.0/0,并且安装了mongoose的最新版本(6.2.6;它应该支持协议(mongodb+srv) )。
当我使用npm start在本地运行时,甚至是从一个被停靠的容器中,这个连接就能很好地工作。但是,当我部署到k8s集群时,会看到一个错误:
querySrv ENOTFOUND _mongodb._tcp.mongodb-cluster0.zvnxj.mongodb.net部署和服务文件如下:
deployment.yml
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: ns-my-workflow-api
name: my-workflow-api
spec:
replicas: 2
selector:
matchLabels:
app: my-workflow-api
template:
metadata:
labels:
app: my-workflow-api
spec:
containers:
- name: my-workflow-api
image: "myname/my-workflow-api:1.0.0"
ports:
- containerPort: 3000
imagePullPolicy: IfNotPresent
resources:
limits:
cpu: "256m" service.yaml的内容如下:
apiVersion: v1
kind: Service
metadata:
namespace: ns-my-workflow-api
name: my-workflow-api
spec:
selector:
app: my-workflow-api
type: LoadBalancer
ports:
- name: http
port: 8000
targetPort: 3000
protocol: TCP namespace.yaml的内容如下:
apiVersion: v1
kind: Namespace
metadata:
name: ns-my-workflow-api我还使用deployment.yaml规则尝试了dns:
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: ns-my-workflow-api
name: my-workflow-api
spec:
replicas: 2
selector:
matchLabels:
app: my-workflow-api
template:
metadata:
labels:
app: my-workflow-api
spec:
dnsPolicy: Default # <------ this rule
containers:
- name: my-workflow-api
image: "myname/my-workflow-api:1.0.0"
ports:
- containerPort: 3000
imagePullPolicy: IfNotPresent
resources:
limits:
cpu: "256m"一旦我将连接url更改为使用2.0.14 or earlier,我就能够连接。连接字符串以mongodb://....启动
虽然我已经设法使用旧的连接字符串来解决这个问题,而且这似乎是某种dns解析问题,但如何使较新的协议从集群内部连接到地图集呢?提前感谢
发布于 2022-03-22 07:34:43
我能够解决这个问题,用它启动minikube
minikube start --driver=docker
似乎底层oracle的virtualbox驱动程序存在一些dns解析问题(可能还有一些配置和设置问题)
https://stackoverflow.com/questions/71545384
复制相似问题