hi all, having some difficulty upgrading my dagste...
# kubernetes
i
hi all, having some difficulty upgrading my dagster helm chart ever since i switched from v3.Release to v4.Chart - replacing ConfigMaps via pulumi does not seem to work:
Copy code
kubernetes:core/v1:ConfigMap (dagster:bl-test/dagster-webserver-env):
    error: resource "urn:pulumi:test::bl::kubernetes:<http://helm.sh/v4:Chart$kubernetes:core/v1:ConfigMap::dagster:bl-test/dagster-webserver-env|helm.sh/v4:Chart$kubernetes:core/v1:ConfigMap::dagster:bl-test/dagster-webserver-env>" was not successfully created by the Kubernetes API server: Server-Side Apply field conflict detected. See <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources> for troubleshooting help.
    The resource managed by field manager "pulumi-kubernetes-f376ca1e" had an apply conflict: Apply failed with 2 conflicts: conflicts with "pulumi-kubernetes-e55deddf":
    - .data.DAGSTER_K8S_PIPELINE_RUN_IMAGE
    - .metadata.labels.chart
i just deleted the config maps that were failing the replace operation... not really sure I understand all the plumbing here
h
did you edit those configs with kubectl, or were you replacing some configs left over from the v3.release?
i
I did a full down/up when going from v3.release -> v4.chart however i believe this error had something to do with a new version of the helm chart being released & i currently don't pin to a specific version during development - but it still doesn't explain the error as it should be able to handle a new version of a chart without renaming the field managers
h
interesting, do you happen to know which version you were on previously? was it 1.8.6→1.8.7? that will give us something to potentially reproduce it.
i
it was 1.8.6 -> 1.8.7 🙂