https://pulumi.com
Join Slack
This message was deleted.
# pulumi-kubernetes-operator
s
This message was deleted.
b
the only thing I found is this warning
so, in case of manual execution, I would run 
pulumi refresh
and 
pulumi up
to re-created deleted bucket
but how to achieve the same with pulumi operator ?
Copy code
const mystack = new k8s.apiextensions.CustomResource("stack3", {
    apiVersion: '<http://pulumi.com/v1|pulumi.com/v1>',
    kind: 'Stack',
    spec: {
        stack: stackName,
        projectRepo: stackProjectRepo,
        resyncFrequencySeconds: 60,
        refresh: true,
        //branch: "refs/heads/master",
        branch: "master",
        envRefs: { ...
b
Hi ! In our case, we added 
resyncFrequencySeconds: 240
. It will automatically refresh and update the stack every 240 seconds, even if no change is detected from git repo (https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/docs/stacks.md)
b
yes, I have this variable in my code 
resyncFrequencySeconds: 60,
b
My bad, I didn’t see you already had the variable in your Stack
b
well, in mentioned pulumi example old operator version is used
Copy code
image: "pulumi/pulumi-kubernetes-operator:v1.0.0",
upgrading to 1.8.0 fixed the issue
@brainy-beach-36627 thank you for taking a look anyway)
e
The operator does not do drift detection by default. You need to set the field 
ContinueSyncOnCommitMatch
in the stack object; then it will run the stack, whether or not the commit or branch HEAD has changed.
8 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by