Code Monkey home page Code Monkey logo

Comments (7)

juan131 avatar juan131 commented on September 24, 2024 1

That's the problem @cnocula-peg ... You're setting for http the same port used by default by the chart for https, hence the duplication.

from charts.

juan131 avatar juan131 commented on September 24, 2024

Introduced at #25969

from charts.

juan131 avatar juan131 commented on September 24, 2024

Hi @cnocula-peg

Are you using a custom server block? Does your solution returns a non-200 HTTP code when you accessing to /?

from charts.

cnocula-peg avatar cnocula-peg commented on September 24, 2024

Hi @juan131,
we are not doing anything special. Plain Helm installation into an AWS EKS cluster:

          helm repo add bitnami https://charts.bitnami.com/bitnami
          helm search repo bitnami
          helm upgrade "docs-${{ env.product }}-my-app" bitnami/nginx --install --atomic --timeout 3m --create-namespace --namespace "docs-${{ env.product }}-my-app" \
          --set image.registry=${{ env.account }}.dkr.ecr.eu-central-1.amazonaws.com \
          --set image.repository=docs-${{ env.product }}-my-app-${{ env.environment }} \
          --set image.tag=${{ env.imageVersion }} \
          --values docs/values.yaml \
          --values docs/${{ env.environment }}/values.yaml

The values contain mostly Ingress annotations and service port definitions.

The server block is also pretty much default:

serverBlock: |-
  server {
    listen       8443 ssl;

    ssl_certificate      bitnami/certs/server.crt;
    ssl_certificate_key  bitnami/certs/server.key;

    ssl_session_cache    shared:SSL:1m;
    ssl_session_timeout  5m;

    ssl_ciphers  HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers  on;

    location / {
      root   html;
      index  index.html index.htm;
    }
  }

I had to pin the helm upgrade to --version 17.0.2 to make our deployment work again.

from charts.

cnocula-peg avatar cnocula-peg commented on September 24, 2024

@dgomezleon unfortunately your fix still does not work for me with chart version 17.2.0.

During the helm upgrade call, I now get a warning:

W0523 10:46:11.468665 16278 warnings.go:70] unknown field "spec.template.spec.containers[0].readinessProbe.path"

And I am still getting the 400 / Bad Request on the readiness probe:

10.0.2.157 - - [23/May/2024:10:46:21 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:26 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:31 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:36 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:41 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:46 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:51 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"
10.0.2.157 - - [23/May/2024:10:46:56 +0000] "GET / HTTP/1.1" 400 248 "-" "kube-probe/1.28+" "-"

Rendered output:

        app.kubernetes.io/version: 1.26.0
        helm.sh/chart: nginx-17.2.0
...
        livenessProbe:
          failureThreshold: 6
          initialDelaySeconds: 30
          periodSeconds: 10
          successThreshold: 1
          tcpSocket:
            port: http
          timeoutSeconds: 5
        name: nginx
        ports:
        - containerPort: 8443
          name: http
          protocol: TCP
        - containerPort: 8443
          name: https
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /
            port: http
            scheme: HTTP
          initialDelaySeconds: 5
          periodSeconds: 5
          successThreshold: 1
          timeoutSeconds: 3

P.S.
By the way, I also get an (unrelated) warning in a different place:
W0523 10:46:11.468694 16278 warnings.go:70] spec.template.spec.containers[0].ports[1]: duplicate port definition with spec.template.spec.containers[0].ports[0]

from charts.

juan131 avatar juan131 commented on September 24, 2024

@cnocula-peg thanks for reporting it! This PR should address the issue you're facing right now: #26394

Regarding the container ports? Could you share the values you're using ?

from charts.

cnocula-peg avatar cnocula-peg commented on September 24, 2024

These are my service and container section values.

service:
  type: NodePort
  ports:
    http: 8443
  targetPort:
    http: 8443

containerPorts:
  http: 8443

from charts.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.