Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trident-Operator Deployment - configurator-reconcile-interval #924

Open
LeonardPoiana opened this issue Sep 4, 2024 · 1 comment
Open

Comments

@LeonardPoiana
Copy link

LeonardPoiana commented Sep 4, 2024

We are not using the auto generated backends and we end up with a failed trident-opeator pod because of the :

  • -configurator-reconcile-interval={{ .Values.configuratorReconcileInterval }}

Trident-Operator Deployment

  • command:
    • /trident-operator
    • -configurator-reconcile-interval={{ .Values.configuratorReconcileInterval }}
      {{- if .Values.operatorDebug }}
    • -debug

configuratorReconcileInterval is the resource refresh rate for the auto generated backends.
configuratorReconcileInterval: 30m0s

We recommend to include a condition when needs to ran

Leonard Poiana

@Utkarshjh
Copy link
Contributor

@LeonardPoiana We are interested to know the steps which causes the trident-operator pod to go in failed state. Unless we don't have tconf CR (which will come only when we enable auto backend config) we should never land in this place. It would be very helpful if we could get the steps to reproduce and operator logs as well. Thank you.

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

No branches or pull requests

3 participants