• Robert Everson

    Robert Everson

    1 month ago
    Does anyone else use the
    namespaceTemplate
    option for the k8s-array plugin in flytepropeller? We’re on a rather old version, but I’m seeing that flyteadmin is only using the parent namespace for the resources it creates, so when we override the
    namespaceTemplate
    in our clusterresource templates in flyteadmin, we are now seeing an error that the namespace is incorrect (our templates have the namespaceTemplate manually applied to them, so the verification of creating the resource fails as the namespace on the Template and the namespace on the object differ). This might just be an issue with using 2 different versions of flyteadmin and flytepropeller, but wanted to check if this is expected.
  • k

    katrina

    1 month ago
    what do you mean by "parent namespace for the resources it creates" ? flyteadmin should use that ns template mapping when creating flyteworkflow CRDs in addition cluster resource controller namespaced-objects
  • are you seeing the cluster resource controller fail to sync the state of the world? that alone should hopefully be orthogonal to the k8s plugin config value 🙂
  • Robert Everson

    Robert Everson

    1 month ago
    sorry, just saw this update. So we have a bunch of templates in flyteadmin to be applied to the namespace, but I don’t see any of them get applied to the
    project-domain-subtask
    namespace that is used for
    k8sArray
    tasks.