Hey folks, we're currently in the process of testi...
# flyte-deployment
r
Hey folks, we're currently in the process of testing out an upgrade from the 1.9.1 chart -> 1.11.0, and we're hitting the following error when propeller is coming up:
Copy code
{
  "json": {},
  "level": "panic",
  "msg": "failed to load plugin - container: [PluginInitializationFailed] wrong type. Actual: *cache.multiNamespaceInformer",
  "ts": "2024-04-30T20:25:09Z"
}
Is this saying that it's failing to include the default
container
plugin, ie: https://github.com/flyteorg/flyte/blob/db1182142e473836f47fa3a8b376a10fc6ef8386/charts/flyte-core/values.yaml#L791-L795? We're not currently overriding any of these default values (apart from omitting the
agent-service
), but curious if others have hit this / if there's a recommended fix
Relevant snippet from our values:
Copy code
enabled_plugins:
        tasks:
          task-plugins:
            enabled-plugins:
              - container
              - sidecar
              - k8s-array
            default-for-task-types:
              container: container
              sidecar: sidecar
              container_array: k8s-array
g
@David Espejo (he/him) ^
d
@Rahul Mehta I'm trying to find what change could have triggered this behavior. Could you confirm if you're trying to migrate to
1.11.0-b0
or
1.11.1-b1
?
r
Just
1.11.0
, didn't try the
b0
or
b1
variants
Are those hotfixes or other RCs? not familiar w/ that versioning scheme
d
@Rahul Mehta are you using
limit-namespace
?
r
Ah, yeah we are - this is due to the fact that we also run a staging instance in the same cluster (so we can test out upgrades against prod data w/ the same RBAC/other constraints, vs a dev environment which isn't always representative). Did something change in these versions w/ the
limit-namespace
behavior?
d
yeah, a recent update caused a bug that's fixed. The fix should be out in the next release
r
Awesome, thanks for clarifying @David Espejo (he/him)!
Circling back, upgrading to 1.12.0 worked. Thanks for the ongoing assistance @David Espejo (he/him) / team!