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.

Sign up for GitHub

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

Jump to bottom

The haproxy_pod.yaml.j2 template produces a broken yaml #3

Closed
rascasoft opened this issue May 31, 2024 · 0 comments · Fixed by #4
Closed

The haproxy_pod.yaml.j2 template produces a broken yaml #3

rascasoft opened this issue May 31, 2024 · 0 comments · Fixed by #4

Comments

@rascasoft
Copy link
Member

If k8s_ingress_nginx_haproxy_conf is set to true, then the haproxy.yaml produced is broken, as follows:

  containers:
  - image: haproxy:2.8
    name: haproxy
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: localhost
        path: /healthz
        port: 8443
        scheme: HTTPS
        securityContext:
      capabilities:
        add:
        - NET_BIND_SERVICE
      runAsUser: 0
        volumeMounts:
    - mountPath: /usr/local/etc/haproxy/haproxy.cfg
      name: haproxyconf
      readOnly: true

This must be fixed.
rascasoft added a commit that referenced this issue May 31, 2024
@rascasoft
Fix the haproxy pod yaml format
3d5ada5 
This fixes the structure of the yaml when k8s_ingress_nginx_haproxy_conf is set
to true.

Fixes: #3
@rascasoft rascasoft mentioned this issue May 31, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix the haproxy pod yaml format mmul-it/kubelab
1 participant
@rascasoft