NATS Manager

Manages the lifecycle of a NATS JetStream deployment.

Description

NATS Manager is a standard Kubernetes operator that observes the state of NATS JetStream deployment and reconciles its state according to the desired state.

How It Works

This project aims to follow the Kubernetes Operator pattern.

It uses Controllers, which provide a reconcile function responsible for synchronizing resources until the desired state is reached on the cluster.

This project is scaffolded using Kubebuilder, and all the Kubebuilder makefile helpers can be used.

Installation

1. To install the latest version of the NATS manager on your cluster, run:

   kubectl apply -f https://github.com/kyma-project/nats-manager/releases/latest/download/nats-manager.yaml

2. To install the latest version of the default NATS CR on your cluster, run:

   kubectl apply -f https://github.com/kyma-project/nats-manager/releases/latest/download/nats_default_cr.yaml

Development

Prerequisites

• Go
• Docker
• kubectl
• Kubebuilder
• kustomize
• Access to Kubernetes cluster (k3d / Kubernetes)

Run NATS Manager locally

1. Download Go packages:

   go mod vendor && go mod tidy

2. Install the CRDs into the cluster:

   make install

3. Run your NATS Manager (this will run in the foreground, so if you want to leave it running, switch to a new terminal).

   make run

   NOTE: You can also run this in one step by running: make install run

Run tests

Run the unit and integration tests:

make generate-and-test

Linting

1. Fix common lint issues:

   make imports
   make fmt

2. Run lint check:

   make lint

Modify the API definitions

If you are editing the API definitions, generate the manifests such as CRs or CRDs using:

make manifests

NOTE: Run make --help for more information on all potential make targets.

For more information, see the Kubebuilder documentation.

Build container images

Build and push your image to the location specified by IMG:

make docker-build docker-push IMG=<container-registry>/nats-manager:<tag> # If using docker, <container-registry> is your username.

NOTE: Run the following for MacBook M1 devices:

make docker-buildx IMG=<container-registry>/nats-manager:<tag>

Deployment

You’ll need a Kubernetes cluster to run against. You can use k3d to get a local cluster for testing, or run against a remote cluster.

NOTE: Your NATS Manager automatically uses the current context in your kubeconfig file, that is, whatever cluster kubectl cluster-info shows.

Deploy on the Cluster

1. Download Go packages:

   go mod vendor && go mod tidy

2. Install the CRDs to the cluster:

   make install

3. Build and push your image to the location specified by IMG:

   make docker-build docker-push IMG=<container-registry>/nats-manager:<tag>

4. Deploy the nats-manager controller to the cluster:

   make deploy IMG=<container-registry>/nats-manager:<tag>

5. [Optional] Install NATS Custom Resource:

   kubectl apply -f config/samples/eventing-nats-eval.yaml

Undeploy NATS Manager

Undeploy the NATS Manager from the cluster:

make undeploy

Uninstall CRDs

To delete the CRDs from the cluster:

make uninstall

Deploy NATS Manager Module With Kyma Lifecycle Manager

1. Deploy the Lifecycle Manager to the Kubernetes cluster:

   kyma alpha deploy

2. Apply the NATS module template to the Kubernetes cluster:

   NOTE: You can get the latest released module template, or you can use the module template from the artifacts of nats-module-build job either from the main branch or from your pull request.

   kubectl apply -f module-template.yaml

3. Enable the NATS module:

   kyma alpha enable module nats -c fast -n kyma-system

4. If you want to verify whether your NATS module is deployed properly, perform the following checks:

   • Check if the NATS resource has the ready state:

     kubectl get -n kyma-system nats

   • Check if the Kyma resource has the ready state:

     kubectl get -n kyma-system kyma

Uninstall NATS Manager Module With Kyma Lifecycle Manager

1. Delete NATS Custom Resource (CR) from the Kubernetes cluster (if exists):

   kubectl delete -n kyma-system nats eventing-nats

2. Disable the NATS module:

   kyma alpha disable module nats

3. Delete the NATS module template:

   kubectl get moduletemplates -A
   kubectl delete moduletemplate -n <NAMESPACE> <NAME>

4. Check whether your NATS module is uninstalled properly:

   • Make sure that the NATS Custom Resource (CR) does not exist. If it exists, then check the status of NATS CR:

     kubectl get -n kyma-system nats eventing-nats -o yaml

   • Check if the Kyma resource has the ready state:

     kubectl get -n kyma-system kyma

E2E Tests

NOTE: Because the E2E tests need a Kubernetes cluster to run on, they are separated from the remaining tests and are only executed if the e2e build tags are passed.

For the E2E tests, provide a Kubernetes cluster and run:

make e2e IMG=<container-registry>/nats-manager:<tag>

If you already have deployed the NATS-Manager on your cluster, you can simply run:

make e2e-only

To adjust the log level, use the environment variable E2E_LOG_LEVEL. It accepts the values debug, info, warn and error. The default value is debug. To set the level, enter:

export E2E_LOG_LEVEL="error"

The E2E test consists of four consecutive steps. You can run them individually as well.

1. To set up a NATS CR and check that it and all correlated resources like Pods, Services and PVCs are set up as expected, run:

   make e2e-setup

2. To execute a bench test on the NATS-Server, run:

   make e2e-bench

   This relies on the setup from make e2e-setup.

   NOTE: Running this on slow hardware like CI systems or k3d clusters results in poor performance. However, this is still a great tool to simply show that NATS JetStream is in an operational configuration.

3. To check that the internals of the NATS-Server are healthy and configured as expected, run:

   make e2e-nats-server

   This will rely on the setup from make e2e-setup.

4. To clean up the test environment and to check that all resources correlated to the NATS CR are removed, run:

   make e2e-cleanup

Contributing

See CONTRIBUTING.md

Code of Conduct

See CODE_OF_CONDUCT.md

Licensing

See the License file