Deployment of helm chart istio-base never goes to the ready state even though it is successful

Open
#6,058 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, helm, kubernetes

Research direction

Start by running the provided helm_resource script and observing the UI and resource_deps behavior. Trace how the istio-base Helm deployment reports readiness after Helm completes; done means it reaches ready rather than server-pending, and UI builds and resource dependencies proceed.

Written by the indexing model from the issue text.

Description

bug

load('ext://helm_resource', 'helm_resource', 'helm_repo')
helm_repo('istio', 'https://istio-release.storage.googleapis.com/charts')
helm_resource('istio-base', 'istio/base', namespace='istio-system', flags=["--version", "1.17.1"])

Simply run this script and check the ui, notice it stays stuck on "server-pending" even though it has completed it's work successfully. This blocks ui builds and well as resource_deps.

Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tilt-dev/tilt

All issues in tilt-dev/tilt

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.