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
We have our standard install.yaml file (at config/install.yaml) which incorporates the numaflow CRDs in it (see this line). We can have another one for users who have already installed numaflow CRDs separately (as through our AddOn).
This should be done prior to this, such that the automation can actually grab from the install.yaml which does not include the numaflow CRDs.
Motivation: If we use our current install.yaml file (at config/install.yaml) from Numaplane, it includes the Numaflow CRDs in it, which we don't want. Those should come from the Numaflow repository.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Summary
We have our standard install.yaml file (at config/install.yaml) which incorporates the numaflow CRDs in it (see this line). We can have another one for users who have already installed numaflow CRDs separately (as through our AddOn).
This should be done prior to this, such that the automation can actually grab from the install.yaml which does not include the numaflow CRDs.
Motivation: If we use our current install.yaml file (at config/install.yaml) from Numaplane, it includes the Numaflow CRDs in it, which we don't want. Those should come from the Numaflow repository.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: