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

[BUG] front pod error #249

Open
Hokwang opened this issue Apr 24, 2023 · 4 comments
Open

[BUG] front pod error #249

Hokwang opened this issue Apr 24, 2023 · 4 comments
Labels
bug Something isn't working pending answer

Comments

@Hokwang
Copy link

Hokwang commented Apr 24, 2023

Describe the bug
Hi,

I want to install mailu. This is first time.
I don't want to use tls, cert-manager, ...

In my values.yaml

ingress:
  tls: false
  selfSigned: false

and then, after install, there's error.

k -n mailu describe pod mailu-front-5dfd8d4bfb-ch6h8
...
Warning  FailedMount  55s (x9 over 3m3s)  kubelet            MountVolume.SetUp failed for volume "certs" : secret "mailu-certificates" not found

front pod alway have a volume

volumes:
- name: certs
secret:
items:
- key: tls.crt
path: cert.pem
- key: tls.key
path: key.pem
secretName: {{ include "mailu.certificatesSecretName" . }}

But there's no secret.

Environment

  • AWS EKS

Additional context

@Hokwang Hokwang added the bug Something isn't working label Apr 24, 2023
@fastlorenzo
Copy link
Collaborator

Hi @Hokwang any reason why you don't want to use self-signed TLS? it's still better than no TLS at all

@chickenandpork
Copy link

Hi @Hokwang, it seems the deployment for mail does not switch out the TLS config.

Of course, the error is caused by the deployment looking for the secret to mount as a volume, even though you don't want to use TLS (which, as @fastlorenzo implies, is a concerning decision without understanding your reasons or constraints).

If you create a secret with empty values, allowing the deployment to mount a volume (that can be ignored), does your deployment complete ?

@outbackdingo
Copy link

the issue here, is the default is set to false in the chart, so it will always fail .. unless you manually change it to true, so i cant blame the guy if you turned it off by mistake.. i ran into the exact same issue and had to turn selfSigned: false to selfSigned: true... fix the chart.

@PPCM
Copy link

PPCM commented Nov 13, 2024

Hello,
I have the same issue. I can explain the raison: I use HAProxy in front for all my web applications, so I don't need HTTPS but HTTP connexion (HAProxy provides the HTTPS connexion)
@chickenandpork You said to create a secret with empty values, I did it, but how to pass the setup to values.yaml?

I tryed

ingress:
  annotations: {}
  apiVersion: ''
  enabled: true
  existingSecret: ''
  extraHosts: []
  extraPaths: []
  extraRules: []
  extraTls: []
  ingressClassName: ''
  path: /
  pathType: ImplementationSpecific
  proxyProtocol:
    imap: false
    imaps: false
    manageSieve: false
    pop3: false
    pop3s: false
    smtp: false
    smtps: false
    submission: false
  realIpFrom: ''
  realIpHeader: X-Forwarded-For
  secrets: [mailu-certificates]
  selfSigned: true
  tls: false
  tlsFlavorOverride: ''

With mailu-certificates the secret with empty values, but the installation fails

Thanks for your help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pending answer
Projects
None yet
Development

No branches or pull requests

5 participants