provider-nats

provider-nats is a Crossplane Provider that implements NATS Jetstream managed resources

Features

Currently the provider supports the following resources:

• Stream: https://docs.nats.io/nats-concepts/jetstream/streams
• Consumer: https://docs.nats.io/nats-concepts/jetstream/consumers

Future releases might implement the key/value store and the object store as well. PRs are welcome.

🎯 Installation

Make sure you have Crossplane installed. See the Crossplane installation guide

Create a Provider resource:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-nats
spec:
  package: ghcr.io/edgefarm/provider-nats/provider-nats:master
  packagePullPolicy: IfNotPresent
  revisionActivationPolicy: Automatic
  revisionHistoryLimit: 1

NOTE: Instead of using package version master have a look at the available versions

📖 Examples

You might find the examples directory helpful. Every example in this directory is deployable in a make dev environment.

For a full spec of possible options

• go to docs.crds.dev for Stream and docs.crds.dev for Consumer
• use the kubectl explain command
• or look at the type definitions apis/consumer/v1alpha1/consumer/consumer_types.go, apis/stream/v1alpha1/stream/stream_types.go

# How to use kubectl explain
$ kubectl explain streams.nats.crossplane.io.spec.forProvider
$ kubectl explain consumers.nats.crossplane.io.spec.forProvider

You can also follow the NATS Jetstream configuration docs and NATS Jetstream consumer configuration docs for more information as the managed resources implement basically the same configuration options.

Example stream resource

apiVersion: nats.crossplane.io/v1alpha1
kind: Stream
metadata:
  name: foo
spec:
  forProvider:
    domain: foo
    config:
      subjects:
        - foo.>
      retention: Limits
      storage: File
      maxBytes: 102400
      discard: Old
  providerConfigRef:
    name: default

Example minimal pull consumer resource

apiVersion: nats.crossplane.io/v1alpha1
kind: Consumer
metadata:
  name: pull
spec:
  forProvider:
    stream: foo
    config:
      pull: {}
  providerConfigRef:
    name: default

Developing locally

Start a local development environment using kind with crossplane and a complete NATS environment. Ensure that you can reach nats.nats.svc on 127.0.0.1

# The provider needs to know how to reach the NATS server. We use kubectl port-forward to expose the NATS server on localhost
echo "nats.nats.svc" >> /etc/hosts
# Create the cluster
make dev
# Please ensure you reach the right cluster before we start the port-forward. Usually it should be the right one after `make dev`
kubectl port-forward -n nats svc/nats 4222:4222

Once the environment is up and running you can deploy the provider and the managed resources. Have a look at the files used to e2e tests (cluster/local/e2e/manifests/).

🐞 Debugging

Just start the debugger of your choice to debug cmd/provider/main.go. The only thing that is important is, that your KUBECONFIG points to a dev cluster with the CRDs deployed (see Developing locally).

🧪 Testing

Simply run make e2e for running the e2e tests. The e2e tests spin up a kind cluster with a fully provisioned NATS environment including leaf nats servers and JWT/NKEY based authentication. The e2e tests ensure that managing streams and consumers works as expected.

If you want to develop or debug e2e tests you have some options for the creation of the test cluster.

Provide the following env variables for make e2e:

• E2E_DEV: if true, the e2e cluster is not deleted after the tests
• E2E_SKIP_TESTS: if true, the e2e tests are skipped

To create a cluster that is capable of running the e2e tests and keep it running during development of the e2e tests you can combine both:

E2E_DEV=true E2E_SKIP_TESTS=true make e2e

🤝🏽 Contributing

Code contributions are very much welcome.

1. Fork the Project
2. Create your Branch (git checkout -b AmazingFeature)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature")
4. Push to the Branch (git push origin AmazingFeature)
5. Open a Pull Request targetting the beta branch.