emqxarchive/emqx-chart

emqx kubernetes helm

The code for this project has been migrated to emqx/emqx and this project is no longer maintained

emqx-chart's Issues

Please use helm default property release namespace instead of a extra namespace property

I think you should use the helm integrated (helm)release namespace property instead of using the extra one defined in your values.yaml.

helm upgrade --install --devel emqx \
             --namespace emqx \
             emqx/emqx

Installing a application with helm this way would normaly lead to all resources placed into the right namespace. In the case of emqx all resources are created in the default namespace.

Error: apiVersion 'v2' is not valid. The value must be "v1"

Unable to install emqx via helm chart repo

Versions:

Helm: v2.15.2
Kubernetes: v1.16.2

Error thrown while installing helm chart for emqx via the following steps:

helm repo add emqx https://repos.emqx.io/charts
helm install --namespace iot-pipeline --name emqx -f values-production.yaml emqx/emqx --devel

Error:
Error: apiVersion 'v2' is not valid. The value must be "v1"

Scale up cpu usage

When scaling up an emqx deployment from the chart (haven't tested anything else), new instances take up 100% cpu on the host (1 full thread/core).

   PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command          
 40883 ldiamond   20   0   760     8     0 R 98.8  0.0  0:56.65 erl_child_setup 1073741816 

values.yaml nodeSelector duplicated in master branch

nodeSelector: {} is duplicated in values.yaml in master branch

Activation of EMQ-X modules

Can an example be provided on how we can properly configure the helm chart to allow the use of plugins for EMQ-X? I'm specifically looking for how to use the username/password plugin against a MongoDB database; however, I believe that having something that may be slightly more generic in nature, or more encompassing, may be a better alternative.

Thanks.

Deploy a persistent EMQ X cluster not working.

Hi Team,

Followed this article https://www.emqx.io/blog/69 and tried deploying persistent emqx cluster with Storage Classes resources on GKE. Already set up the helm. Installing emqx by this command:

$ helm install --devel --name chat-group-emqx --set image=emqx/emqx:v3.2.3 --set emqxAddressType=hostname --set persistence.enabled=true --set persistence.storageClass=group-emqx-sc emqx/emqx

However, facing the below error:

Error: render error in "emqx/templates/StatefulSet.yaml": template: emqx/templates/StatefulSet.yaml:70:28: executing "emqx/templates/StatefulSet.yaml" at <.Values.image.repository>: can't evaluate field repository in type interface {}

Please note: Storage class already exists named group-emqx-sc(and in default namespace.)

$: kubectl get sc
NAME                 PROVISIONER            AGE
group-emqx-sc        kubernetes.io/gce-pd   62m

Kindly let me know if I am missing on anything.

Chart installation failed

Helm install chart failed with error: helm no matches for kind "StatefulSet" in version "apps/v1beta1"
with helm v2.14.3 & Kubernetes v1.16.0

Error: Wait helm template failed

Hi I tried to install EMQX with helm catalog on rancher.
Now when i started the service i see the following error message:

'Wait helm template failed. Error: stat /emqx: no such file or directory : exit status 1'

Any idea what i can do wrong?

Submit into main helm repository

Curious if the author of this script has thought about adding it into the main helm chart repository at https://github.com/helm/charts ... It would make it more discoverable, as we looked through that repository to see if something was available, when it was not, a google search brought us here.

Just my $0.02 on the subject. YMMV and all the other good fodder that comes along with a question like this.

Thanks.

K8s v1.22.4 failed to install

Getting wrong ingress api version when installing on 1.22
reconciliation failed: Helm upgrade failed: current release manifest contains removed kubernetes api(s) for this kubernetes version and it is therefore unable to build the kubernetes objects for performing the diff. error from kubernetes: unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"