Waldemar Quevedo

## Defect Make sure that these boxes are checked before submitting your issue -- thank you! - [x] Included `nats-server -DV` output - [x] Included a [Minimal, Complete, and Verifiable...

Fixes to RespondMsg usage when crossing accounts

5

When receiving a request, if the msg is responded using the `RespondMsg` API, the published response currently accidentally includes the inbox of the original request which will not be used,...

Improve support for consumer FilterSubjects

10

Given the following Stream setup with wildcards: ```go js.AddStream(&nats.StreamConfig{ Name: "foo", Subjects: []string{"foo.*", "foo"}, }) ``` Using the JS context, currently there is no way to subscribe to set a...

NATS Operator and K8S v1.20 compatibility

2

Users have reported that some of the features from the operator like service roles have stopped working on K8S 1.20 ``` E0527 15:18:55.677376 1 generic.go:108] error syncing "nats-io/nats-cluster": failed to...

Support websockets

1

Can already be used with nightly images

Support gateways to private networks

1

Currently gateways require to use a public ip, should also support using $KUBERNETES_NODE_IP as the advertise address in case everything is in private networks.

Schema validation

2

Look into a way to be able to detect for wrong configuration fields that may be part of the NatsCluster manifest.

Need a similar configuration block like the helm charts ```yaml leafnodes: enabled: true remotes: - url: tls://connect.ngs.global:7422 credentials: secret: name: ngs-creds key: NGS.creds ```

Change api version from `nats.io/v1alpha2` to `nats.io/v1`

1

Now that Kubernetes v1.12 is available and pid namespace feature can be used, I think reasonable to start looking into bumping the CRD api version to beta.