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
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:
The problem was because we were migrating from V1 with a scenario involving two Pulumi Operators separated by namespaces. In V2, this is no longer allowed:
With the 2.0 release, the supported installation modes are limited to a cluster-wide installation. You’ll need to be a cluster admin to install the Operator. The Operator is able to handle stacks across all the namespaces of your cluster.
Another point of attention for those using Helm and S3 as backend state and are migrating to V2 is that previously, in our values.yaml, we had:
However, this is not propagated to the new workspace pods. In our case, it was necessary to include the environment variable in the Stack objects like this:
Additionally, the method for setting the log level has changed. It took us some time to realize this, which delayed our debugging efforts. Previously, we used:
Thanks @mateusvtt, I took some time to incorporate your feedback into the migration guide.
Since beta 3, some of the causes of the "object has been modified" message were fixed. The message doesn't necessarily represent a problem, just a symptom. I'm going to close this now, and please re-open if you have more details after updating to the latest build.
What happened?
Customer sees this error after applying a
Stack
resource to the cluster:Example
Customer applied this
Stack
:Output of
pulumi about
Customer installed the operator via Helm:
Additional context
Related:
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: