We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have VMAuth with tls enabled and with:
apiVersion: operator.victoriametrics.com/v1beta1 kind: VMAuth metadata: name: vmauth namespace: monitoring spec: image: tag: v1.99.0 secrets: - vmauth-cert extraArgs: tls: "true" tlsCertFile: /etc/vm/secrets/vmauth-cert/tls.crt tlsKeyFile: /etc/vm/secrets/int-vmauth-cert/tls.key
the container spec has:
livenessProbe: failureThreshold: 10 httpGet: path: /health port: 8427 scheme: HTTP periodSeconds: 5 successThreshold: 1 timeoutSeconds: 5 readinessProbe: failureThreshold: 10 httpGet: path: /health port: 8427 scheme: HTTPS periodSeconds: 5 successThreshold: 1 timeoutSeconds: 5
So the livenessProbe doesn't have proper scheme while readinessProbe does. As a result the container keeps crashing.
livenessProbe
scheme
readinessProbe
The operator image is docker.io/victoriametrics/operator:v0.42.2
docker.io/victoriametrics/operator:v0.42.2
The text was updated successfully, but these errors were encountered:
Must be fixed at v0.42.0 release
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I have VMAuth with tls enabled and with:
the container spec has:
So the
livenessProbe
doesn't have properscheme
whilereadinessProbe
does. As a result the container keeps crashing.The operator image is
docker.io/victoriametrics/operator:v0.42.2
The text was updated successfully, but these errors were encountered: