Skip to content

Conversation

@Coderxrohan
Copy link

@Coderxrohan Coderxrohan commented Jan 31, 2026

Issue:
Ceph-CSI includes a legacy liveness driver and related deployment artifacts (sidecar containers, Services, ServiceMonitors, and documentation) that are no longer needed. Kubernetes now provides native liveness and health probing, making the custom liveness driver redundant.

Fix:

  1. Removed all references to the deprecated liveness driver across the repository:
  2. Deleted liveness sidecar containers from RBD, CephFS, and NFS manifests
  3. Removed liveness-related Services and ServiceMonitors
  4. Cleaned up documentation sections describing liveness metrics and endpoints
  5. Ensured generated YAMLs no longer expose unused metrics ports

Impact:

  • Simplifies CSI deployments by relying on Kubernetes-native health checks
  • Avoids exposing unused ports and services
  • Reduces maintenance burden and configuration complexity
  • Aligns Ceph-CSI with current Kubernetes best practices

Level:
Medium-severity cleanup / technical debt reduction

Fixes: #5599

@Coderxrohan Coderxrohan force-pushed the cleanup-liveness-driver branch from e4f0c49 to aa19fd2 Compare January 31, 2026 19:48
Copy link
Collaborator

@Madhu-1 Madhu-1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Coderxrohan Thanks for the work, did you get a chance to verify that profing endpoint works if we remove it? what about the code in the liveness.go?

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Feb 2, 2026

This is kind of a breaking change, we need to add it to Pending release notes. cc @Rakshith-R @nixpanic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove liveness driver type from the ceph-csi

2 participants