Flux v2.2.0 Provider v1beta3 API is not backwards compatible with v1beta2

[n-asenov]

Describe the bug

Upgrading a Provider from v1beta2 to v1beta3 API fails if the Provider has an interval field set in its spec.

Steps to reproduce

Upgrade the following Provider from v1beta2 to v1beta3

---
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Provider
metadata:
  name: alertmanager
  namespace: flux-system
spec:
  interval: 10m
  type: alertmanager
  address: http://kube-prometheus-stack-alertmanager.monitoring.svc.cluster.local:9093/api/v2/alerts/

The upgrade fails with

Provider/flux-system/alertmanager dry-run failed: failed to create typed patch object (flux-system/alertmanager; notification.toolkit.fluxcd.io/v1beta3, Kind=Provider): .spec.interval: field not declared in schema...

Expected behavior

Provider v1beta3 API should be backward compatible with v1beta2 and the upgrade should pass without errors.

Screenshots and recordings

No response

OS / Distro

N/A

Flux version

v2.2.0

Flux check

N/A

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[darkowlzz]

Thanks for reporting this issue. Sorry for the inconvenience.
.spec.interval was an optional field in v1beta2 Provider unlike other flux API objects. It was unusual to set, hence missed in our upgrade testing. I tried reproducing it and this happens only when interval is explicitly set.

I've created fluxcd/notification-controller#683 to add interval back in v1beta3 Provider. We'll do a patch release which should fix this.

[fenio]

When do you plan patch release?
Or what's workaround for it?

[hiddeco]

The work around for it is quite literally to remove the field from your Provider resources, as it is deprecated and will (even when added back) be no longer used.

[stefanprodan]

When do you plan patch release?

Yes somewhere this week