Skip to content

feat(helm): date label-sourced releases from object metadata - #176

Merged
mayankpande88 merged 1 commit into
mainfrom
feat/labels-first-deployed
Nov 18, 2026
Merged

mayankpande88 merged 1 commit into
mainfrom
feat/labels-first-deployed

Conversation

@mayankpande88

Copy link
Copy Markdown
Contributor

Description

Releases found with --release-source labels had zero first/last deployed times, so the installed date in nova find output was 0001-01-01T00:00:00Z.

  • First deployed: the earliest creation time among the release's labelled objects.
  • Last deployed: the latest managedFields time written by the helm field manager on any of those objects. Helm writes it on install and on each upgrade that changes the object. When no helm write is recorded, it falls back to first deployed.
  • The Secrets source is unchanged.

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

How to verify: run nova find --release-source labels --format json and check that each release's Installed.date is a real timestamp, not 0001-01-01T00:00:00Z.

Engineering detail
  • Last deployed can trail the real upgrade time. An upgrade that changes none of the labelled objects (e.g. a values change that only touches a Secret) doesn't update their helm managedFields time.
  • Tests cover earliest-creation selection, a missing creation time, the fallback when no helm write is recorded, and picking the latest helm time (other managers ignored). go test ./... and golangci-lint run are clean.

Local e2e: ran the built binary against a real multi-release cluster while impersonating a service account without Secrets access. Before: all 37 releases had 0001-01-01. After: none did, and 27 of 37 installed dates fell on the same day as Helm's own last-deployed time from the Secrets source; the other 10 were earlier, as described above.

Checklist

  • I have updated/added any relevant documentation (CHANGELOG)

Releases found with --release-source labels had zero first/last deployed
times, so the installed date in the output was 0001-01-01. Take first deployed
from the earliest creation time of the release's objects and last deployed
from the latest managedFields time written by the helm field manager, falling
back to first deployed when no helm write is recorded.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds deployment date tracking for label-sourced Helm releases by capturing the earliest creation time of the release's objects as 'FirstDeployed' and the latest update time by the 'helm' field manager as 'LastDeployed'. It updates the internal structures, implements helper functions to parse managed fields, and includes unit tests verifying this behavior. There are no review comments, and I have no feedback to provide.

@mayankpande88
mayankpande88 merged commit 0c2040e into main Nov 18, 2026
4 checks passed
@mayankpande88
mayankpande88 deleted the feat/labels-first-deployed branch November 18, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants