Skip to content
Snippets Groups Projects
Select Git revision
  • 4f4f0d70a41e56d8b11e5f4ec1dcd2ae76d89c7f
  • main default protected
  • release/v2.7.x
  • release/v2.6.x
  • conform-k8s-1.33
  • release/v2.5.x
  • release/v2.4.x
  • remove-notation-validation
  • release/v2.3.x
  • release/v2.2.x
  • RFC
  • fix-commit-log
  • flux-audit
  • release/v2.1.x
  • context-ns
  • ksm-dashboard
  • rfc-passwordless-git-auth
  • release/v2.0.x
  • rfc-gating
  • release/v0.27.4
  • rfc-0003
  • v2.7.2 protected
  • v2.7.1 protected
  • v2.7.0 protected
  • v2.6.4 protected
  • v2.6.3 protected
  • v2.6.2 protected
  • v2.6.1 protected
  • v2.6.0 protected
  • v2.5.1 protected
  • v2.5.0 protected
  • v2.4.0 protected
  • v2.3.0 protected
  • v2.2.3 protected
  • v2.2.2 protected
  • v2.2.1 protected
  • v2.2.0 protected
  • v2.1.2 protected
  • v2.1.1 protected
  • v2.1.0 protected
  • v2.0.1 protected
41 results

kustomization.go

Blame
  • user avatar
    Hidde Beydals authored
    This should prevent the generation of the object getting bumped, as
    observed on a GKE K8s 1.18 cluster using the  logic before this commit.
    
    We only want to generation to increase when there are actual changes to
    the `spec` of a resource, as some controllers use the `generation`
    value to make assumptions about what they should do during a
    reconciliation.
    
    Signed-off-by: default avatarHidde Beydals <hello@hidde.co>
    9607b07e
    History
    kustomization.go 1.37 KiB