brainy-window-77332
01/20/2022, 2:16 PMsparse-park-68967
01/21/2022, 1:24 AMbrainy-window-77332
01/26/2022, 11:38 AMsparse-park-68967
01/26/2022, 9:19 PMcontinueResyncOnCommitMatch
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/branchwonderful-portugal-96162
02/17/2022, 3:16 AMapiVersion: <http://pulumi.com/v1|pulumi.com/v1>
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: <https://github.com/christianh814/pulumi-k8s-operator-example>
branch: "refs/heads/main"
destroyOnFinalize: true
retryOnUpdateConflict: true
continueResyncOnCommitMatch: true
resyncFrequencySeconds: 30
refresh: true
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?pulumi up
so maybe this is a generic thing...
https://pulumi-community.slack.com/archives/C84L4E3N1/p1645114639793099pulumi config set kubernetes:enableDryRun true --stack dev
fixed my issue (until that's the default behavior)quiet-wolf-18467
02/18/2022, 8:03 AMwonderful-portugal-96162
02/18/2022, 2:52 PMsparse-park-68967
02/18/2022, 10:11 PMquiet-wolf-18467
02/19/2022, 4:29 PM