Shulou(Shulou.com)05/31 Report--

How to deploy ripstack to k8s with helm chart, for this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more small partners who want to solve this problem find a simpler and easier way.

chirpstack-helm-chart

Open source lorawan server project chirpstack helm chart , project source code

how to contribute

If you want to contribute to the project, click the fork button to fork the project and launch a PR.

Fork

Contributed to Preparations:Fork this project.

Contribution Flow $ git remote add chirpstack-helm-chart git@github.com:liangyuanpeng/chirpstack-helm-chart.git

# sync with the remote master

$ git checkout master

$ git fetch chirpstack-helm-chart

$ git rebase chirpstack-helm-chart/master

$ git push origin master

# create a PR branch

$ git checkout -b your_branch

# do something

$ git add [your change files]

$ git commit -sm "xxx"

$ git push origin your_branch mount helm chart$ git clone https://github.com/liangyuanpeng/chirpstack-helm-chart.git

$ cd chirpstack-helm-chart/

# install helm chart from this repo

$ helm install chirpstack .

Note: By default storageClass named longorn is used for storage.

$ kubectl get po

#After executing the command, you can see the following pod

NAME READY STATUS RESTARTS AGE

chirpstack-as-84b68cb7fd-zgs5j 1/1 Running 0 45s

chirpstack-ns-7d9b9867f-zftn6 1/1 Running 0 45s

mosquitto-0 1/1 Running 0 45s

pgsql-0 1/1 Running 0 45s

redis-0 1/1 Running 0 45s

redis-exporter-64f8bf4f46-2rcgl 1/1 Running 0 45s$ kubectl get svc

#After executing the command, you can see the following svc

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE

chirpstack-as ClusterIP 10.98.227.61 8080/TCP,8001/TCP,8003/TCP 77s

chirpstack-ns ClusterIP 10.108.182.238 8000/TCP 77s

mosquitto ClusterIP 10.104.149.103 1883/TCP 77s

pgsql ClusterIP 10.102.33.231 5432/TCP 77s

redis ClusterIP 10.109.138.95 6379/TCP 77s

redis-exporter ClusterIP 10.106.66.131 9121/TCP 77s$ kubectl get pvc

#After executing the command, you can see the following PVC

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE

pgsql-pvc-pgsql-0 Bound pvc-c1c6adf4-32ef-4431-bd6a-3825a6ef408c 96Mi RWO longhorn 3d

redis-pvc-redis-0 Bound pvc-e464d0e8-e04a-4958-858e-5efef1aeba9c 48Mi RWO longhorn 3d$ helm list

#After executing the command, you can see the following chart

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION

chirpstack default 1 2021-01-29 16:11:48.984574857 +0800 CST deployed chirpstack-helm-chart-0.1.0 1.16.0 Expose svc of application-server, visit application-serverkubectl port-forward svc/chirpstack-as 8080:8080 --address 0.0.0.0 Set network-server on application-server

You can set it to chirpstack-ns. {namespace}:8000 or chirpstack-ns. {namespace}.svc.cluster.local:8000

Here {namespace} is replaced with a real namespace

If you use gateway-bridge, you can expose svc with kubectl expose deploy gateway-bridge --port 1700 --target-port=1700 --protocol=UDP --name udp service--type=NodePort

ChirpStack has been deployed on K8S so far. By default, SVC is created but not further exposed. The specific exposure method is currently left to the user to choose. You can access AS after exposing the AS port. The same is true for MQTT service and gateway-bridge service. Data needs to be uploaded to the server and the service needs to be exposed.

About how to use the helm chart to deploy chipstack to k8s on the answer to the question shared here, I hope the above content can be of some help to everyone, if you still have a lot of doubts not solved, you can pay attention to the industry information channel to learn more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.