v0.8.0

This new version brings a lot of fixes and updates: our controllers have been updated, security fixes have been applied, hostnames are now being resolved prior to registering, and many more features.

v0.7.0

This new version of the CN-WAN Operator brings support for AWS Cloud Map, enabling the project to reflect services inside your cluster to AWS's service registry.

Take a look to our changelog for a complete list of changes.

v0.6.0

v0.6.0 removes the old way of filtering namespaces to be watched with a more intuitive way: instead of using concepts like allowlist or blocklist, one can just set true or false in the new watchNamespacesByDefault. The old labels used to filter them are now dropped in favor of just operator.cnwan.io/watch with values enabled or disabled. Please refer to our documentation to know how this works.

The old, deprecated way to provide options for Google Service Directory is now definitively removed and some other packages have been removed as well, making the project slimmer and smoother.

For a full list of changes, please consult our CHANGELOG.

v0.5.1

v0.5.1 brings some internal improvements and bug fixes to the operator.

Refer to the changelog for a full detail of the changes.

v0.5.0

v0.5.0 makes it easier for you to deploy the operator on your cluster as it does not need any dependency injected into it anymore, i.e. ConfigMaps and Secrets will now be automatically retrieved from the cluster.

Additionally, in case you are running the operator on GKE and choosing to use Service Directory you may now leave some of the settings empty and the operator will detect your project ID and region automatically and therefore set up Service Directory without you having to touch anything.

Some other minor improvements are also present, look at the Changelog to learn more.

v0.4.0

v0.4.0 introduces the ability to retrieve cloud metadata. Not to be confused with service registry metadata, these values provide context about the cloud provider and/or Kubernetes cluster platform that hosts the applications, including the CN-WAN Operator.

This change enables the operator to register some of those metadata -- i.e. the network and sub-network and, in future, more data -- as service registry metadata to be consumed by third party applications, such as the CN-WAN Reader and the CN-WAN Adaptor.

v0.3.0

Version v0.3.0 brings support for the popular key-value store etcd: you can set the CN-WAN Operator to use etcd as your service registry.

To get a list of minor changes as well, please read our Changelog and our documentation.

v0.2.1

Version v02.1 brings some improvements to security aspects and continues the effort to make the project lighter: as a matter of fact, the CN-WAN Operator is now asking for the minimum permissions from Kubernetes, i.e. just reading and listing resource and not modify anything, and uses its own Service Account.

Additionally, it removes dependency from code and structures that were inherited from Kube Builder and that are not currently used.

To get a list of minor changes as well, please read our Changelog and our documentation.