* `github.com/fluxcd/pkg/apis/meta` to `v0.6.0`
* `github.com/fluxcd/source-controller/api` to `v0.6.0`
* `helm.sh/helm/v3` to `v3.5.0`
* `k8s.io/*` to `v0.20.2`
* `sigs.k8s.io/controller-runtime` to `v0.8.0`
Signed-off-by: Hidde Beydals <hello@hidde.co>
To include a bug fix to the `ReconcilateAtChangedPredicate`
and renaming to `ReconcileRequestedPredicate`.
Signed-off-by: Hidde Beydals <hello@hidde.co>
This commit bundles the `helm-controller:$VER-arm64` ARM image tag
range that was previously released separately with the
`helm-controller:$VER` image, as GitHub now provides us insights into
image layer statistics.
Signed-off-by: Hidde Beydals <hello@hidde.co>
This commit upgrades the `controller-runtime` dependency to `v0.7.0`,
including all changes required to make all wiring work again.
- Upgrade `runtime` to v0.6.0 to include `controller-runtime` changes.
- Loggers have been removed from the reconcilers and are now retrieved
from the `context.Context` passed to the `Reconcile` method and
downwards functions.
- Logger configuration flags are now bound to the flag set using
`BindFlags` from `runtime/logger`, ensuring the same contract across
GitOps Toolkit controllers, and the `--log-json` flag has been
deprecated in favour of the `--log-encoding=json` default.
- The `ChangePredicate` from `runtime` has changed to a
`ReconcilateAtChangedPredicate`, and is now chained with the
`GenerationChangedPredicate` from `controller-runtime` using
`predicate.Or`.
- Signatures that made use of `runtime.Object` have changed to
`client.Object`, removing the requirement to e.g. call
`runtime.Object#Object`.
- The `leader-election-role` was changed, as leader election now works
via the `coordination/v1` API.
Other notable changes:
- `util.ObjectKey` was added to easily construct a `client.ObjectKey` /
`types.NamespacedName` from a `metav1.Object`.
Signed-off-by: Hidde Beydals <hello@hidde.co>
To a total of 10 minutes (600s), this allows most release process that
just have been started and make use of the default timeouts to finish.
In a future release, we will likely want to be able to stop a
reconciliation process between the reconciliation steps and continue on
the pod restart (e.g. upgrade -> terminate -> start -> continue with
test).
Signed-off-by: Hidde Beydals <hello@hidde.co>
Hidde Beydals