v1.3.0

Features:

• Add support for Argo Rollout resources: the controller is able to change or add the .spec.restartAt field that causes Argo Rollout restarts the workload

Contributors:
@sebastocorp @achetronic

v1.2.0

Changes:

• Delete legacy deploy directory. This was used in the previous versions to allow Kustomize to deploy Rabbit Stalker using remote manifests. Now, we are publishing manifests bundles directly in the releases. This will make the manifests atomic.
• Implement bundle-build on Makefile
• Add deprecation notice for directory deploy and update README reflecting all deployment possibilities
• Automate artifacts (bundles, binaries, Docker images) building in releases flow
• Docker images are now published in Github Container Registry

Contributors:
@sebastocorp @achetronic

v1.1.0

Changes:

• Add patch constructor pattern: now we correlate a workload type with a function that return a structure PatchConstructorPatchT. This structure contains the type of the patch that will be performed, and the patch itself. This will provide some advantages:
  • Avoid nested conditionals structure (avoid branch miss-prediction)
  • Improve support for new workload types, as they can decide the strategy that suits well for them
  • Fancy code, bro 😎

Contributors:
@sebastocorp @achetronic

v1.0.0 🐰 [welcome home, bunny]

Breaking Changes:

• apiVersion field has changed from rabbit-stalker.docplanner.com/v1alpha1 to rabbit-stalker.prosimcorp.com/v1alpha1: This decision was taken to complete the first steps of integrating the whole project into the Prosimcorp umbrella.
• Documentation up-to-date

v0.4.0 💊

Changes:

• spec.rabbitConnection.vhost is now optional on regex-based searches for queue name

• Now it's possible to use credentials located in different namespaces. When a namespace is not defined on credentials' Secret reference, the controller will use the same namespace where the WorkloadAction CR's is located. For that, two new fields were added:

  • spec.rabbitConnection.credentials.username.secretRef.namespace
  • spec.rabbitConnection.credentials.password.secretRef.namespace

• New predicate added to the controller to avoid enqueue WorkloadAction events when they are only triggered by status updates. More info here

• Improve some status.conditions and the checks done before throwing them. Done to give better information to the user and fix some situations where the controller broke unexpetedly

  • The controller does not explode on unknown URL schemes anymore
  • Default scheme is set to https when not defined in the URL
  • Some StatusConditions where introduced
    • NoQueueFound
    • RequiredFieldNotFound

• Improve documentation on README

v0.3.0 💊

• Changes:
  • Support Regex on queue name searches. This feature is supported using the flag spec.rabbitConnection.useRegex together with the spec.rabbitConnection.queue field due to the endpoint and the behaviour change for static and for regex on RabbitMQ Admin API
  • Documentation added about this feature on README
  • Some status.conditions messages have been refactored to give better insight of the failures (when there are problems)

v0.2.0 💊

• Bug Fixes:

  • Sync process sometimes crashed because in some cases templateAnnotations (inside the workload object) was not present. It's solved now by initializing the variable to an empty map structure when not defined.

• Changes:

  • Add the spec.additionalSources field in WorkloadAction CRD. This field represents a list of of Kubernetes object references.
    Referenced objects will be added to an internal Sources list which will be available into spec.condition.value

  • In addition to the previous point, we needed the capability in spec.condition.value to look for information from inside Sources, using GJSON, and have the possibility to use information coming from all the sources at once to craft complex conditions. Due to this, we introduced a pattern called search structure [<list-index>]{{ <GJSON-expression> }} whose replacements will happen just before evaluating the condition (more information inside README)

• Contributors
  @sebastocorp

v0.1.1 💊

Changes:

• Include Kustomize manifests inside deploy directory to allow deployments from remote without Helm
• Include some samples on README:
  • How to use GJSON conditionals over non-array values
  • How to deploy using Kustomize from remote

Fixes:

• Permissions on ClusterRole. Some typo on the apiGroups field

v0.1.0 💊

First release:

The features are well described in the README file, so we will start from here 🚀

Notes:

• Docker images are being created for several architectures now: linux/amd64, linux/arm64, linuxs390x, linux/ppc64le for those having special servers out there