kubernetes-csi/docs

Define a deprecation policy for csi sidecars

msau42 opened this issue · 4 comments

It can mirror the Kubernetes policy.

Define policy on:

  • sidecar CLI arguments
  • sidecar behavior
  • compatibility with K8s
  • compatibility with CSI spec

This may also tie into defining our sidecar versioning scheme and what warrants a major, minor and patch version bump.

/assign
cc @jsafrane @pohly @saad-ali

  • RBAC policy changes (e.g. new leader election).
pohly commented

"CLI arguments", "RBAC policy" and "CSI spec" can all be considered as "compatibility with existing deployments": if a deployment swaps out the current version of a sidecar with a newer one, will the deployment still work?

"compatibility with K8S" is an extended version of that question: will the deployment still work on the same clusters as before?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/lifecycle frozen