Skip to content

Troubleshooting#

Below you will find some common issues customers have observed and the recommended remediations.

Resource gets stuck due to failed patching - Kustomize Force#

If a coordinated resource fails to deploy, the resource won't continue trying until resolved with intervention.

You can try working around this by either setting .spec.force in your kustomize or by either labelling or annotating kustomize.toolkit.fluxcd.io/force: enabled. This will instruct the contoller to replace the resources if patching fails due to an immutable change.

Although it may be convenient to leave this on enabled permanently, it is considered best practice to remove it after resolution. If left continuously enabled, it may prevent other conflicts or immutable properties from becoming apparent.

kustomize.yaml 

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- main.yml
spec:
  force: enabled

annotations and labels 

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    kustomize.toolkit.fluxcd.io/force: enabled
  annotations:
    kustomize.toolkit.fluxcd.io/force: enabled