Coder Social home page Coder Social logo

Comments (3)

hiddeco avatar hiddeco commented on June 5, 2024 3

Your installation timed out, if the installation takes a long time to complete you can increase the timeout by either setting spec.timeout or spec.install.timeout to a higher value (e.g. timeout: 10m).

from helm-controller.

jam01 avatar jam01 commented on June 5, 2024

Eventually...

Status:
  Conditions:
    Last Transition Time:          2020-11-20T18:30:34Z
    Message:                       Helm install failed: timed out waiting for the condition
    Reason:                        InstallFailed
    Status:                        False
    Type:                          Ready
    Last Transition Time:          2020-11-20T18:30:34Z
    Message:                       Helm install failed: timed out waiting for the condition
    Reason:                        InstallFailed
    Status:                        False
    Type:                          Released
  Failures:                        15
  Helm Chart:                      flux-system/postgresql-jam01
  Install Failures:                1
  Last Attempted Revision:         9.8.11
  Last Attempted Values Checksum:  26b52db786511f9fefc219d38376f0b8cc69e562
  Last Release Revision:           1
  Observed Generation:             2
Events:
  Type    Reason  Age                    From             Message
  ----    ------  ----                   ----             -------
  Normal  info    6m37s (x2 over 6m37s)  helm-controller  HelmChart 'flux-system/postgresql-jam01' is not ready
  Normal  error   95s                    helm-controller  Helm install failed: timed out waiting for the condition
  Normal  error   95s                    helm-controller  reconciliation failed: Helm install failed: timed out waiting for the condition
  Normal  error   12s (x14 over 95s)     helm-controller  reconciliation failed: install retries exhausted

here's the helm controller pod
kubectl describe pod helm-controller -n flux-system

Name:         helm-controller-856b876466-4zvx4
Namespace:    flux-system
Priority:     0
Node:         ip-172-20-94-241.ec2.internal/172.20.94.241
Start Time:   Fri, 20 Nov 2020 11:06:21 -0600
Labels:       app=helm-controller
              pod-template-hash=856b876466
Annotations:  prometheus.io/port: 8080
              prometheus.io/scrape: true
Status:       Running
IP:           100.104.0.2
IPs:
  IP:           100.104.0.2
Controlled By:  ReplicaSet/helm-controller-856b876466
Containers:
  manager:
    Container ID:  docker://2c63b565976cee0da01e8ddf593512a07f799fb3b54e9f8166b0df8f791582fb
    Image:         ghcr.io/fluxcd/helm-controller:v0.3.0
    Image ID:      docker-pullable://ghcr.io/fluxcd/helm-controller@sha256:9207b9f7df35c7b0e58e53d12fbe589d9981d5225c46050c42432fc11908a20e
    Port:          8080/TCP
    Host Port:     0/TCP
    Args:
      --events-addr=http://notification-controller/
      --watch-all-namespaces=true
      --log-level=info
      --log-json
      --enable-leader-election
    State:          Running
      Started:      Fri, 20 Nov 2020 11:06:25 -0600
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  1Gi
    Requests:
      cpu:     100m
      memory:  64Mi
    Liveness:  http-get http://:http-prom/metrics delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      RUNTIME_NAMESPACE:  flux-system (v1:metadata.namespace)
    Mounts:
      /tmp from temp (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-pk7m8 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  temp:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  default-token-pk7m8:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-pk7m8
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  kubernetes.io/arch=amd64
                 kubernetes.io/os=linux
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

from helm-controller.

jam01 avatar jam01 commented on June 5, 2024

Ah! I assumed these were related...

HelmChart 'flux-system/postgresql-jam01' is not ready
Helm install failed: timed out waiting for the condition

My mistake, thank you 🙏

from helm-controller.

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.