https://pulumi.com
Join Slack
Trying out the Pulumi Operator V2 with Git Source with branch option and default resyncFrequencySeco...
# pulumi-kubernetes-operator
s
Trying out the Pulumi Operator V2 with Git Source with branch option and default resyncFrequencySeconds. After a successful updated stack. Is the stack supposed to update when there are new commits to the branch? Currently doesn't seem to appear to sync when new commits are coming in without having to either update the CRD or restarting the workspace pod.
image.png
h
this should definitely trigger an update. what does the stack’s 
.status
field look like?
s
Copy code
status:
  conditions:
  - lastTransitionTime: "2024-11-11T21:51:24Z"
    message: the stack has been processed and is up to date
    reason: ProcessingCompleted
    status: "True"
    type: Ready
  lastUpdate:
    failures: 0
    generation: 6
    lastAttemptedCommit: -
    lastResyncTime: "2024-11-11T21:51:24Z"
    lastSuccessfulCommit: -
    name: -
    state: succeeded
    type: up
h
fwiw we just released a second beta for v2 if you’d like to give that a try, although i can’t guarantee that will fix the issue you’re seeing. https://github.com/pulumi/pulumi-kubernetes-operator/releases/tag/v2.0.0-beta.2
i suggest grabbing some logs from the controller to help narrow down the issue. is the stack’s workspace pod Ready?
quick update - we identified the issue you were running into, and it will be fixed in the upcoming beta.3 release (probably some time later today)
6 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