You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have pulumi-kubernetes-operator managing 4 stacks from 2 TypeScript programs (fetched from git).
Even if there are no changes to the git repo, the pod keeps continuously running npm install
This does not seem desirable.
Example
All screenshots were taken around the same time.
I have the following dependencies in my package.json in the root of the repo where the pulumi programs reside:
Probably not relevant for this case;
I'm using version 0.5.0 via the Helm chart.
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
Thanks for filing the report @v-yarotsky. Have you checked if the issue reproduces on a fresh cluster? It might also be interesting to try to run a manual preview for the stacks to see if there is and to check the interval for the reconcile loop.
After taking a brief look at the code, it seems like this is by design.
On each iteration of the Reconcile loop1, reconcileStackSession.setupWorkspace2 is called, which in turn calls reconcileStackSession.InstallProjectDependencies3. All of that is happening before checking whether the current commit matches the last applied one4.
What happened?
I have pulumi-kubernetes-operator managing 4 stacks from 2 TypeScript programs (fetched from git).
Even if there are no changes to the git repo, the pod keeps continuously running
npm install
This does not seem desirable.
Example
All screenshots were taken around the same time.
I have the following dependencies in my
package.json
in the root of the repo where the pulumi programs reside:Output of
pulumi about
Probably not relevant for this case;
I'm using version 0.5.0 via the Helm chart.
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: