Skip to content

Deploy Kubernetes Helm Charts

active 2023-08-172026-02-18 (UTC)

Complete coverage26,554 / 26,554 hourly files (100%) · 2 absent upstream2023-08-152026-08-25 (UTC)
Events
365
Pushes
0
Pull requests
4
Issues
21
Stars
254
Forks
16

Activity over time

Daily event counts in the loaded window

Line chart, 917 days from 2023-08-17 to 2026-02-18. Pushes: 0 total, peak 0 in a day. Pull requests: 4 total, peak 1 in a day. Issues: 21 total, peak 2 in a day. Comments: 70 total, peak 3 in a day. Stars: 254 total, peak 3 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#1054hitleramini0064-art2026-02-18 23:08
    GPG key ID: 4AEE18F83AFDEB23
  • Issue#2196kauapauloereira-jpg2026-02-15 00:22
    Kaua1233
  • Issue comment#2037meanderix2025-11-28 15:03
    Layering Release Values
  • Issue comment#1817bessny5-cell2025-11-26 16:56
    Possibility to update remote git sources of sub-helmfiles
  • Issue comment#1817bessny5-cell2025-11-26 16:54
    Possibility to update remote git sources of sub-helmfiles
  • Issue#2194Morgimiel2025-08-11 14:06
    Helmfile fetch --output-dir is handled as helmfile.yaml relative path instead of relative to the command
  • Issue#2193juan-ferrer-toribio2025-08-06 07:40
    Set helmfile comandline arguments using `helmfile.yaml` file
  • Issue comment#1924rickymulder2025-07-30 21:05
    Helmfile silently ignores CRDs (and removes them on apply) if strategicMergePatches are used
  • Issue comment#1842jhua042025-06-26 06:41
    remote helmfiles via http (go-getter)
  • Issue#2192dfilipov-glitnor2025-06-13 08:08
    Namespace value from default context not being propagated
  • Issue comment#2192yxxhero2025-06-13 08:05
    Namespace value from default context not being propagated
  • Issue#2191oneaxis2025-06-10 17:28
    Add logged in account feedback for Google Signin in Settings to know which account is being used
  • Issue#2189998877102025-05-22 02:49
    new Helmfile(v1.0.0) failed to run sync with templating error
  • Issue comment#2069chusri2025-04-30 02:07
    [QUESTION] How to pass credentials without declaring in plain text in the repo?
  • Issue comment#658abotau2025-04-22 08:34
    feat: Change the delimiters for state templates and release templates
  • Issue comment#2078TheCodingSheikh2025-04-17 06:38
    Reference other variables in values.yaml.gotmpl
  • Issue comment#2078TheCodingSheikh2025-04-11 11:47
    Reference other variables in values.yaml.gotmpl
  • Issue comment#2185avznog2025-04-01 13:18
    helmfile + aws secrets manager
  • Issue comment#868shcherbak2025-03-15 21:59
    Helm v3 ability to pass --history-max argument on the release level
  • Pull request#2138nagygergo2025-03-15 15:22
  • Issue comment#1329crabique2025-03-09 16:55
    Inject release-specific values into values templates?
  • Pull request#1411jayme-github2025-03-06 13:53
  • Issue comment#1060tmeltser2025-03-05 08:44
    pass-thru options for helmfile template
  • Issue comment#1329dezeroku2025-02-15 23:30
    Inject release-specific values into values templates?
  • Issue comment#2183yxxhero2025-02-13 09:44
    How can i pass multiple Helm values files to a Kutomized Helm Chart ?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 254 stars here means stars gained during the window, not the repo's star count.