# nacos

**Repository Path**: seven-helm/nacos

## Basic Information

- **Project Name**: nacos
- **Description**: nacos from https://github.com/nacos-group/nacos-k8s
- **Primary Language**: Unknown
- **License**: Apache-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-06-25
- **Last Updated**: 2020-12-19

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# 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](https://github.com/nacos-group/nacos-k8s/).

[Important]
 - This is a modified version based on the official version.
 - Requires you to manually install mysql server,but we will help you to init the sql script of the nacos.
 - Only support cluster mode.
 - If you have any questions, please email to i@hanshichao.com

## Prerequisites

 - Kubernetes 1.10+ 
 - Helm v3 
 - PV provisioner support in the underlying infrastructure

## Installing the Chart

To install the chart with `release name`:

```shell
$ helm install `release name` ./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](#configuration) section lists the parameters that can be configured during installation. 

### Service & Configuration Management

#### Service registration
```shell
curl -X POST 'http://$NODE_IP:$NODE_PORT/nacos/v1/ns/instance?serviceName=nacos.naming.serviceName&ip=20.18.7.10&port=8080'
```

#### Service discovery
```shell
curl -X GET 'http://$NODE_IP:$NODE_PORT/nacos/v1/ns/instance/list?serviceName=nacos.naming.serviceName'
```
#### Publish config
```shell
curl -X POST "http://$NODE_IP:$NODE_PORT/nacos/v1/cs/configs?dataId=nacos.cfg.dataId&group=test&content=helloWorld"
```
#### Get config
```shell
curl -X GET "http://$NODE_IP:$NODE_PORT/nacos/v1/cs/configs?dataId=nacos.cfg.dataId&group=test"
```



> **Tip**: List all releases using `helm list`

## Uninstalling the Chart

To uninstall/delete `release name`:

```shell
$ helm uninstall `release name`
```
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                             |
|---------------------------------------|--------------------------------------------------------------------|-------------------------------------|
| `mysql.host`                   | Mysql  host                                       | `mysql.mysql`                              |
| `mysql.database`               | Nacos database name                                                | `nacos_devtest`                     |
| `mysql.user`                   | Nacos database user                                                | `nacos`                             |
| `mysql.password`               | Nacos database password                                            | `nacos`                             |
| `mysql.port`                   | Mysql  port                              | `3306`                                |
| `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`|
| `image.repository`                    | Nacos container image name                                      | `nacos/nacos-server`                   |
| `image.tag`                           | Nacos container image tag                                       | `0.9.0`                                |
| `image.pullPolicy`                    | Nacos container image pull policy                                | `IfNotPresent`                        |
| `env.preferhostmode`                  | Enable Nacos cluster node domain name support                      | `hostname`                         |
| `env.serverPort`                      | Nacos port                                                         | `8848`                               |
| `persistence.enabled`                 | Enable the nacos data persistence or not                           | `false`                              |
| `persistence.data.accessModes` | Nacos data pvc access mode                           | `ReadWriteOnce`                     |
| `persistence.data.resources.requests.storage` | Nacos data pvc requests storage             | `5G`                   |
| `persistence.plugin.accessModes` | Nacos plugin pvc access mode (Available as cluster mode)                       | `ReadWriteOnce`                     |
| `persistence.plugin.resources.requests.storage` | Nacos plugin pvc requests storage (Available as cluster mode)             | `5G`                   |
| `persistence.log.accessModes` | Nacos log pvc access mode (Available as cluster mode)                           | `ReadWriteOnce`                     |
| `persistence.log.resources.requests.storage` | Nacos log pvc requests storage (Available as cluster mode)| `5G`          |
| `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` |