Skip to content

Factor HelmRelease defaults and drift detection into k8s/bases/components/ like the platform #68

Description

@devantler

🤖 Generated by the Daily AI Engineer

Problem. The reference platform DRYs its HelmRelease configuration through reusable Kustomize components (k8s/bases/components/helmrelease-flux-defaults, helmrelease-drift-detection); the template has no components/ directory, so every scaffolded HelmRelease repeats those settings and misses drift detection defaults.

Proposed direction. Port the two components (genericized), wire them into the template's HelmRelease-bearing bases, and note the pattern in the template docs. Also sweep the remaining vendored/raw-manifest infra for HelmRelease candidates now that theme 3's CoreDNS migration (#14 via #62) has landed.

Rough size. M

Part of #24

Activity

  1. coderabbitai commented on Jul 13, 2026

    @coderabbitai
    🔗 Related PRs

    #62 - feat(coredns): migrate docker-provider CoreDNS from Deployment to HelmRelease [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. moved this to 📥 Backlog in 🌊 Project Boardon Jul 18, 2026
  3. added a commit that references this issue on Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions