nacos-k8s

Nacos Helm Chart

Nacos is committed to help you discover, configure, and manage your microservices. It provides a set of simple and useful features enabling you to realize dynamic service discovery, service configuration, service metadata and traffic management.

Introduction

This project is based on the Helm Chart packaged by nacos-k8s.

Prerequisites

Tips

If you use a custom database, please initialize the database script yourself first. https://github.com/alibaba/nacos/blob/develop/distribution/conf/nacos-mysql.sql

Usage

Add repo:

helm repo add nacos https://yunwz.github.io/nacos-k8s
helml repo update

Install nacos application:

$ helm install mynacos nacos/nacos

The command deploys Nacos on the Kubernetes cluster in the default configuration. It will run without a mysql chart and persistent volume. The configuration section lists the parameters that can be configured during installation.

Service & Configuration Management

Login to nacos

curl -X POST 'http://$NODE_IP:$NODE_PORT/v3/auth/user/login?username={your_username}&password={your_password}'

the token will be returned in the response body, like this:

{"accessToken":"eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJuYWNvcyIsImV4cCI6MTc0OTM5MzE1OH0.cHTZzXl9iFHhzLW9TJKFVLt3OxxjcwPBOyd73jI6h-M","tokenTtl":18000,"globalAdmin":true,"username":"nacos"}

Also, you can export the token to environment variable

export accessToken=$(curl -X POST "http://$NODE_IP:$NODE_PORT/v3/auth/user/login?username={your_username}&password={your_password}"|jq -r .accessToken)

Check the token is valid:

echo $accessToken

Service registration

curl -X POST "http://$NODE_IP:$CLIENT_HTTP_NODE_PORT/nacos/v3/client/ns/instance?serviceName=nacos.naming.serviceName&ip=20.18.7.10&port=8080" --header "accessToken: $accessToken"

Service discovery

curl -X GET "http://$NODE_IP:$CLIENT_HTTP_NODE_PORT/nacos/v3/client/ns/instance/list?serviceName=nacos.naming.serviceName" --header "accessToken: $accessToken"

Publish config

curl -X POST "http://$NODE_IP:$NODE_PORT/v3/console/cs/config?dataId=nacos.cfg.dataId&groupName=test&content=helloWorld" --header "accessToken: $accessToken"

Get config

curl -X GET "http://$NODE_IP:$NODE_PORT/v3/console/cs/config?dataId=nacos.cfg.dataId&groupName=test" --header "accessToken: $accessToken"

Tip: List all releases using helm list

Uninstalling the Chart

To uninstall/delete nacos application:

$ helm uninstall mynacos

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following table lists the configurable parameters of the Skywalking chart and their default values.

Parameter Description Default  
global.mode Run Mode (quickstart, standalone, cluster; ) standalone  
resources The [resources] to allocate for nacos container {}  
nodeSelector Nacos labels for pod assignment {}  
affinity Nacos affinity policy {}  
tolerations Nacos tolerations {}  
resources.requests.cpu nacos requests cpu resource 500m  
resources.requests.memory nacos requests memory resource 2G  
nacos.replicaCount Number of desired nacos pods. If run in standalone mode,the replicaCount is not working 3  
nacos.image.repository Nacos container image name nacos/nacos-server  
nacos.image.tag Nacos container image tag v3.0.1  
nacos.image.pullPolicy Nacos container image pull policy IfNotPresent  
nacos.plugin.enable Nacos cluster plugin that is auto scale true  
nacos.plugin.image.repository Nacos cluster plugin image name nacos/nacos-peer-finder-plugin  
nacos.plugin.image.tag Nacos cluster plugin image tag 1.1  
nacos.health.enabled Enable health check or not false  
nacos.preferHostMode Enable Nacos cluster node domain name support hostname  
nacos.serverPort Nacos pod’s port 8848  
nacos.consolePort Nacos console main port 8080  
nacos.mcpPort Nacos mcp registry port 9080  
nacos.authToken Nacos auth plugin token secret key if empty, will use a random string  
nacos.identityKey Nacos auth server identity key if empty, will use a random string  
nacos.identityValue Nacos auth server identity value if empty, will use a random string  
nacos.storage.type Nacos data storage method mysql or embedded. The embedded supports either standalone or cluster mode embedded  
nacos.storage.db.host mysql host    
nacos.storage.db.name mysql database name    
nacos.storage.db.port mysql port 3306  
nacos.storage.db.username username of database    
nacos.storage.db.password password of database    
nacos.storage.db.param Database url parameter characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true&useSSL=false  
persistence.enabled Enable the nacos data persistence or not false  
persistence.data.accessModes Nacos data pvc access mode ReadWriteOnce  
persistence.data.storageClassName Nacos data pvc storage class name manual  
persistence.data.resources.requests.storage Nacos data pvc requests storage 5G  
service.type http service type NodePort  
service.port http service port 8848  
service.nodePort http service nodeport 30000  
ingress.enabled Enable ingress or not false  
ingress.annotations The annotations used in ingress {}  
ingress.hosts The host of nacos service in ingress rule nacos.example.com  
secret.generate if true, will generate a random string for nacos identity key and value and auth token true  
secret.name   if secret.generate is false, you can set an existed secret name. The secret must contains authToken, identityKey and identityValue empty

Example

img

standalone mode(with embedded)

$ helm install mynacos nacos/nacos

img

standalone mode(with mysql)

$ helm install mynacos nacos/nacos --set nacos.storage.db.host=host --set nacos.storage.
db.name=dbName --set nacos.storage.db.port=port --set nacos.storage.db.username=username  --set nacos.storage.db.
password=password

img

Tip: if the logs of nacos pod throws exception, you may need to delete the pod. Because mysql pod is not ready, nacos pod has been started.

cluster mode(without pv)

$ helm install mynacos nacos/nacos --set global.mode=cluster

img

$ kubectl scale sts `release name`-nacos --replicas=3

img

img