tilt-dev / tilt-dev/tilt-extensions

helm_remote: Wait for namespace to exist before moving on

Open
#320 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs repro case
Dominant language
Starlark
Stars
243
Forks
194
Avg merge
3d 4h
Merged PRs (30d)
5

Description

Code:

helm_remote('kafka',
  repo_name='bitnami',
  repo_url='https://charts.bitnami.com/bitnami',
  version='12.17.3',
  release_name='kafka',
  namespace='kafka',
  create_namespace=True,
  set=[
    'deleteTopicEnable=true',
    'defaultReplicationFactor=1',
    'offsetsTopicReplicationFactor=1',
  ]
)
k8s_resource(
  'kafka',
  labels=["databases"]
)
k8s_resource(
  'kafka-zookeeper',
  labels=["databases"]
)

Error:

STEP 1/1 — Deploying
     Applying YAML to cluster

Build Failed: namespaces "kafka" not found

It seems that sometimes it works and sometimes does not. When I triggered update via UI (on kafka resource) it worked. But , the first time when I saved Tiltfile the error occurred.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the helm_remote and k8s_resource entry points and reproduce the first-save deployment using create_namespace=True. Trace the ordering between namespace creation and dependent resource application. Done means the initial deployment no longer fails with “namespaces "kafka" not found” and does not require a UI-triggered update.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.