Question

我现在正在尝试实施新系统。我的系统将分为2个集群。首先是计算工作。 CI / CD将非常频繁地对其进行重大更改。然后防止它发生在我大三生的事故中，还节省了成本。因为在计算机节点上不需要像100GB那样使用database

现在。我正在使用helm来设置mongo-replicaset。我的配置正常。这是我在安装过程中的终端日志。

每个节点安装100GB。它们是3个节点。

$ gcloud container clusters create elmo --disk-size=100GB --enable-cloud-logging --enable-cloud-monitoring

我已经更改了values.yaml中的用户名和密码

mongodbUsername: myuser
mongodbPassword: mypassword

但是，当我跳到吊舱中时。它不需要我进行任何身份验证。我可以执行show dbs

$ kubectl exec -it ipman-mongodb-replicaset-0 mongo

MongoDB shell version v4.0.6
connecting to: mongodb://127.0.0.1:27017/?gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("966e85fd-8857-46ac-a2a4-a8b560e37104") }
MongoDB server version: 4.0.6
Welcome to the MongoDB shell.
For interactive help, type "help".
For more comprehensive documentation, see
    http://docs.mongodb.org/
Questions? Try the support group
    http://groups.google.com/group/mongodb-user
2019-03-20T12:15:51.266+0000 I STORAGE  [main] In File::open(), ::open for '//.mongorc.js' failed with Unknown error
Server has startup warnings:
2019-03-20T11:36:03.768+0000 I STORAGE  [initandlisten]
2019-03-20T11:36:03.768+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2019-03-20T11:36:03.768+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2019-03-20T11:36:05.082+0000 I CONTROL  [initandlisten]
2019-03-20T11:36:05.082+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2019-03-20T11:36:05.082+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2019-03-20T11:36:05.083+0000 I CONTROL  [initandlisten]
---
Enable MongoDB's free cloud-based monitoring service, which will then receive and display
metrics about your deployment (disk utilization, CPU, operation statistics, etc).

The monitoring data will be available on a MongoDB website with a unique URL accessible to you
and anyone you share the URL with. MongoDB may use this information to make product
improvements and to suggest MongoDB products and deployment options to you.

To enable free monitoring, run the following command: db.enableFreeMonitoring()
To permanently disable this reminder, run the following command: db.disableFreeMonitoring()
---

rs0:PRIMARY> show dbs
admin   0.000GB
config  0.000GB
local   0.000GB

我可以看到2个服务正在运行mongodb-replicaset

$ kubectl describe svc ipman-mongodb-replicaset

Name:              ipman-mongodb-replicaset
Namespace:         default
Labels:            app=mongodb-replicaset
                   chart=mongodb-replicaset-3.9.2
                   heritage=Tiller
                   release=ipman
Annotations:       service.alpha.kubernetes.io/tolerate-unready-endpoints: true
Selector:          app=mongodb-replicaset,release=ipman
Type:              ClusterIP
IP:                None
Port:              mongodb  27017/TCP
TargetPort:        27017/TCP
Endpoints:         10.60.1.5:27017,10.60.2.7:27017,10.60.2.8:27017
Session Affinity:  None
Events:            <none>

$ kubectl describe svc ipman-mongodb-replicaset-client

Name:              ipman-mongodb-replicaset-client
Namespace:         default
Labels:            app=mongodb-replicaset
                   chart=mongodb-replicaset-3.9.2
                   heritage=Tiller
                   release=ipman
Annotations:       <none>
Selector:          app=mongodb-replicaset,release=ipman
Type:              ClusterIP
IP:                None
Port:              mongodb  27017/TCP
TargetPort:        27017/TCP
Endpoints:         10.60.1.5:27017,10.60.2.7:27017,10.60.2.8:27017
Session Affinity:  None
Events:            <none>

我看过here和here。我有3个IP地址。我应该使用哪一个？

我认为LoadBalancer可能不适合我的需求，因为它通常与backend服务一起使用以平衡节点之间的负载。就我而言。 master是写作，replica是读书。

$ gcloud compute instances list
NAME                                 ZONE               MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP     STATUS
gke-elmo-default-pool-c5dc6e86-1j8v  asia-southeast1-a  n1-standard-1               10.148.0.59  35.197.148.201  RUNNING
gke-elmo-default-pool-c5dc6e86-5hs4  asia-southeast1-a  n1-standard-1               10.148.0.57  35.198.217.71   RUNNING
gke-elmo-default-pool-c5dc6e86-wh0l  asia-southeast1-a  n1-standard-1               10.148.0.58  35.197.128.107  RUNNING

问题：

为什么我的username:password在进行身份验证时没有考虑？
我如何公开我的mongo shell，并允许来自Internet的客户端通过使用

mongo -u <user> -p <pass> --host kluster.me.com --port 27017

我已经检查了helm chart文档。我担心我以错误的方式使用k8s。因此，我决定在这里询问。

Answer 1

我无法回答密码问题，但是为数据库使用单独的群集可能不是最佳选择。通过创建单独的集群，您不得不将敏感数据库公开。这不理想。

我建议您在现有集群上部署mongo。这样，您只需将服务名称用作主机名，即可将计算工作负载连接到mongo。

如果您的mongo需要更大的驱动器，则在使用helm创建mongo安装时，只需使用持久性磁盘并指定大小即可。

例如：

helm install mongo-replicaset --name whatever --set persistentVolume.size=100Gi

在您的values.yaml文件中，有一个称为persistence的部分，应称为persistentVolume。

我建议您的values.yaml仅包含要更改的值，而不要包含所有内容。

公开具有访问控制权的GKE mongo

1 个答案: