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

VMAgent livenessProbe not using TLS #896

Closed
lassizci opened this issue Mar 9, 2024 · 1 comment · Fixed by #897
Closed

VMAgent livenessProbe not using TLS #896

lassizci opened this issue Mar 9, 2024 · 1 comment · Fixed by #897
Labels
bug Something isn't working

Comments

@lassizci
Copy link
Contributor

lassizci commented Mar 9, 2024

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.

The operator image is docker.io/victoriametrics/operator:v0.42.2

@f41gh7 f41gh7 reopened this Mar 10, 2024
@f41gh7 f41gh7 added the bug Something isn't working label Mar 12, 2024
@f41gh7
Copy link
Collaborator

f41gh7 commented Apr 18, 2024

Must be fixed at v0.42.0 release

@f41gh7 f41gh7 closed this as completed Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants