Skip to content

Releases: argoproj-labs/argo-rollouts-manager

v0.0.4

27 Sep 12:11
Compare
Choose a tag to compare

What's Changed

  • Run the E2E tests that work for both cluster-scoped and namespace-scope modes, on both by @jgwest in #64
  • Switch to quay.io for E2E test image to avoid throttling by @jgwest in #66
  • Add logic to reconcile multiple RolloutMangers by @Rizwana777 in #65
  • ClusterRole/ClusterRoleBinding should be deleted when RolloutManager is deleted by @jgwest in #69
  • Preserve label/annotations on updated Deployments by @jgwest in #71
  • Update to latest release of Argo Rollouts: v1.7.0 by @jgwest in #70
  • Upgrade to Argo Rollouts v1.7.1 by @jgwest in #75
  • Fix '.spec.additionalMetadata' field issue where is is not updating labels/annotations of existing rollouts resources by @Rizwana777 in #76
  • feat - Add option to provide resources requests/limits to controller by @OpenGuidou in #60
  • Fix Service NodePort conflicts when running on large cluster by @jgwest in #80
  • Add/Improve unit tests for controllers/utils.go file by @Rizwana777 in #78
  • (feat) - Add option to not deploy notification secret by @OpenGuidou in #74
  • chore:update operator-sdk and kubebuilder version to match sibling gitops/argocd-operators by @Rizwana777 in #79

Full Changelog: v0.0.3...v0.0.4

v0.0.3

16 Jul 09:31
Compare
Choose a tag to compare

What's Changed

  • Add ginkgo unit tests for configMaps by @Rizwana777 in #40
  • Improve upstream Rollouts E2E test parsing, by allowing test retries by @jgwest in #44
  • Improve logic used to detect changes in Deployment resource by @jgwest in #46
  • build(deps): bump google.golang.org/protobuf from 1.31.0 to 1.33.0 by @dependabot in #50
  • Move OPENSHIFT_ROUTE_PLUGIN_LOCATION to controllers pkg by @jgwest in #52
  • feat: Cluster-scoped Rollouts support by @jparsai in #39
  • Update latest value of OpenShiftRolloutPlugin in ConfigMap by @Rizwana777 in #51
  • Add route to ClusterRole/Role, update plugin name in ConfigMap by @jgwest in #54
  • build(deps): bump golang.org/x/net from 0.17.0 to 0.23.0 by @dependabot in #56
  • Update controller-runtime to v0.16.3 and remove argo-rollout dependency by @Rizwana777 in #53
  • Refactor RolloutManager status update logic to eliminate/reduce failed status update errors by @jgwest in #55
  • Update requirements.txt based on Argo CD version by @jgwest in #58
  • feat: Support additional metadata for controller by @OpenGuidou in #17
  • Add a logic for RolloutManager to create ServiceMonitor by @Rizwana777 in #49
  • Downgrade Prometheus Operator module dependency to same as gitops-operator by @jgwest in #61

New Contributors

Full Changelog: v0.0.2...v0.0.3

v0.0.2

29 Feb 02:51
027faa9
Compare
Choose a tag to compare

What's Changed

  • feat: update the module and import paths to argoproj-labs by @iam-veeramalla in #14
  • integrate openshift route plugin with rollouts manager by @ishitasequeira in #15
  • Add golangci-lint and gosec to Makefile by @jgwest in #18
  • Port Kuttl tests to Ginkgo and enable GH E2E/unit test workflow by @jgwest in #19
  • Upgrade to Argo Rollouts v1.6.4 by @jgwest in #21
  • Add gofmt check and fix branch names by @jgwest in #23
  • Add initial pull request template by @jgwest in #28
  • Run upstream Argo Rollouts E2E tests on argo-rollouts-manager PRs (#30) by @jgwest in #31
  • Upgrade to Argo Rollouts v1.6.5 by @jgwest in #32
  • Update instructions running e2e tests by @jopit in #35
  • Add new e2e tests by @jopit in #36
  • Upgrade to Argo Rollouts v1.6.6 by @jgwest in #38
  • Convert existing unit test to ginkgo in controlller package by @Rizwana777 in #37
  • Add automatic rollouts upgrade script (#33) by @jgwest in #34

New Contributors

Full Changelog: v0.0.1...v0.0.2

Release v0.0.1

10 May 07:56
ccd334d
Compare
Choose a tag to compare
Release v0.0.1 Pre-release
Pre-release

Initial version of Argo Rollout Manager.
A stable version which can manage the life cycle of Argo Rollouts such as Install, Uninstall, Auto Upgrades and Auto healing of any manual changes.

Special Thanks to @jaideepr97 and @drpaneas for the code review and feedback.