No probes for kanister operator

[ifalex]

Is your feature request related to a problem? Please describe.

One of best practice of a Pod is represented by having readines/liveness probes.
Is this something you would consider for kanister-operator deployment?

Describe the solution you'd like

Create readiness/liveness probes for kanister-operator if it makes sense. If it doesn't, provide explanation of why not supported/not needed.

Additional context

Many lint tools (kube-linter, kube-score) report this as critical issue.

[github-actions]

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

[anishbista60]

@pavannd1
IMO , we should go for using probes since the Many lint tools (kube-linter, kube-score) report this as critical issue and generally it is best practice to do so.

However, we do have some not doing aspect.

• Operator doesnot need to have serve more traffic like traditional application. So, defination for probes might be differ here.
• So on

I need the proper feedback from maintainer regarding should we use probe or not ? . So , that i can work in this Issue.