Drift Detection

It is possible to automatically detect drift in deployments by using the driftDetection, see the following example

manifests/claims/s3bucket.yaml

apiVersion: infraweave.io/v1
kind: S3Bucket
metadata:
  name: my-s3-bucket
spec:
  ...
  driftDetection:
    enabled: true
    interval: 10m
    autoRemediate: true
    webhooks:
      - url: "https://hooks.slack.com/triggers/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"

It is possible to enable/disable and set interval for the checks.

Tip

Drift detection works regardless of how it was deployed (GitOps, CLI, Python or Kubernetes), it is checked periodically in the platform.

Auto Remediation

It is possible to auto-remediate the drift by setting autoRemediate to true

manifests/claims/s3bucket.yaml

...
spec:
  ...
  driftDetection:
    ...
    autoRemediate: true

Caution

Use with caution. This is dangerous to use in production environments, as it can lead to destructive events. In critical environments: monitor for changes and approve them after being reviewed.

Drift Webhooks

It is possible to set up webhooks to be called when drift is detected, which can be useful for e.g. use with slack

manifests/claims/s3bucket.yaml

...
spec:
  ...
  driftDetection:
    webhooks:
      - url: "https://hooks.slack.com/triggers/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"
      - url: "multiple_urls_can_be_added"