From 715e7a80710e87a66820de1ffb015a521b2dcd70 Mon Sep 17 00:00:00 2001 From: afeiszli Date: Wed, 20 Jul 2022 08:41:25 -0400 Subject: [PATCH] removing singlenode by default --- .helmignore | 5 +++++ README.md | 5 +++++ values.yaml | 2 +- 3 files changed, 11 insertions(+), 1 deletion(-) create mode 100644 .helmignore diff --git a/.helmignore b/.helmignore new file mode 100644 index 0000000..54b8449 --- /dev/null +++ b/.helmignore @@ -0,0 +1,5 @@ +# comment + +# Match any file or path named .git +.git + diff --git a/README.md b/README.md index cc0246e..bc7fd85 100644 --- a/README.md +++ b/README.md @@ -13,6 +13,11 @@ To run HA Netmaker on Kubernetes, your cluster must have the following: - Nginx Ingress + LetsEncrypt/Cert-Manager - Traefik Ingress + LetsEncrypt/Cert-Manager - to generate automatically, make sure one of the two is configured for your cluster +- Access to modify the Load Balancer for external traffic: + - By default, MQ is deployed with a NodePort, and DNS must point to this NodePort + - If deploying with default settings, you must modify the cluster load balancer so that it will load balancer 31883 --> 31883 + - Alternatively, you can specify "singlenode=true" in your helm options. In this case, a node must be labelled with mqhost=true. + - If this option is selected, you do not have to modify your loadbalancer, but you MUST modify DNS settings to point broker.domain to the public IP of the node running MQ. Also note that this will not be an HA MQ deployment. Furthermore, the chart will by default install and use a postgresql cluster as its datastore: diff --git a/values.yaml b/values.yaml index 6f9f967..a64d502 100644 --- a/values.yaml +++ b/values.yaml @@ -41,7 +41,7 @@ ui: mq: # -- how many MQTT replicas to create replicas: 2 - singlenode: true + singlenode: false storageSize: 128Mi