Does the operator support drift detection

Question

sparse-park-68967 · Answer

Could you expand what you mean by drift detection You want the defined stack settings to stomp on external modifications automatically

brainy-window-77332 · Answer

Sorry for delay distracted by client work yes If any changes are made to the infrastructure managed via Pulumi I d want it to be restored to the state defined in the pulumi source code yaml that the operator is applied Obviously you d want this to be an optional feature that could be enabled

sparse-park-68967 · Answer

So we have a means to do this now but I haven t tried it explicitly You can set the new `continueResyncOnCommitMatch` field on a stack and track a branch instead of a specific commit This will cause the stack to be resynced periodically even if desired state specified in the HEAD commit on that branch has been reached You can also set the `resyncFrequencySeconds` field to set the frequency with which this resync should occur You will want to enable the `refresh` option to force pulumi to refresh its state from the backing resource during a resync to detect a drift After which it should assert the state backed to the desired state in the backing repository branch

wonderful-portugal-96162 · Answer

So I came here to ask this very question and I m trying these settings but it s not changing it back to the desired state ```apiVersion kind Stack metadata name nginx k8s stack spec envRefs PULUMI ACCESS TOKEN type Secret secret name pulumi api secret key accessToken stack christianh814 quickstart dev projectRepo branch refs heads main destroyOnFinalize true retryOnUpdateConflict true continueResyncOnCommitMatch true resyncFrequencySeconds 30 refresh true```

wonderful-portugal-96162 · Answer

The code golang deploys the NGINX deployment with one replica But when I scale it to 3 ```k scale deployment nginx j2wvuiws replicas=3``` It never goes back down to 1 ```$ k get pods l app=nginx NAME READY STATUS RESTARTS AGE nginx j2wvuiws 85b98978db dx4l7 1 1 Running 0 5m43s nginx j2wvuiws 85b98978db sr8m8 1 1 Running 0 6m47s nginx j2wvuiws 85b98978db zljgg 1 1 Running 0 5m43s``` Running `pulumi stack history` shows that it is running every 30 seconds like I put in my config above Am I missing something

wonderful-portugal-96162 · Answer

So I saw the same behavior with `pulumi up` so maybe this is a generic thing <https pulumi community slack com archives C84L4E3N1 p1645114639793099>

wonderful-portugal-96162 · Answer

Just an update doing `pulumi config set kubernetes enableDryRun true stack dev` fixed my issue until that s the default behavior

quiet-wolf-18467 · Answer

I m not really sure why that fixed it I wouldn t expect that to change anything

wonderful-portugal-96162 · Answer

I m not 100 sure either Not sure how Pulumi calculates diff If it uses the same 3way diff Kuberentes does or if it uses something else But the behavior is was Without that config I experienced the above behavior

sparse-park-68967 · Answer

Sorry I missed this yes dry run would help here See <https github com pulumi pulumi kubernetes issues 694>

quiet-wolf-18467 · Answer

TIL