You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 1.7.0 and 1.8.0 release notes seem to contradict each other.
1.7.0 claims it was the first to use server-side apply, and its usage is unconditional.
This is the first version of cert-manager which relies on Server-Side Apply. We use it to properly manage the annotations and labels on TLS secrets.
1.8.0 also claims it was the first to use server-side apply, and its usage is behind a feature gate.
cert-manager v1.8.0 adds initial support for Kubernetes Server-Side Apply, which became stable in Kubernetes 1.22. This support is behind a feature gate for now, and is only supported by cert-manager on Kubernetes 1.22 and later.
Does 1.7 actually use server-side apply? If so, is it behind a feature gate or not? What exactly did 1.8 change with respect to server-side apply?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The 1.7.0 and 1.8.0 release notes seem to contradict each other.
1.7.0 claims it was the first to use server-side apply, and its usage is unconditional.
1.8.0 also claims it was the first to use server-side apply, and its usage is behind a feature gate.
Does 1.7 actually use server-side apply? If so, is it behind a feature gate or not? What exactly did 1.8 change with respect to server-side apply?
Beta Was this translation helpful? Give feedback.
All reactions