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
There is a desire to use Cloud Workspaces to create a development environment on a VM where there is a k3d environment running.
What @kohlisid has in mind is that when somebody spins up one of these, it would deploy the Numaflow AddOn, and then deploy everything identical to that which is being deployed to other environments. While Cloud Workspaces does not require the "no data loss" features of Numaplane, the deployment through this means is seen as being more seamless.
There is no ArgoCD. One issue I can think of is that we no longer have the Sync Waves in that case. This would mean that a Pipeline can in fact be deployed without a corresponding isbsvc, and thus would enter a "Failed" state.
Perhaps, we could add a check before creating a Pipeline that the isbsvc exists and has been fully reconciled.
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:
BTW, @kohlisid and I did discuss the potential of not using Numaplane at all, but that seemed less seamless (he would need to go fetch the numaflow manifest himself, he would deploy differently from the other environments).
Summary
There is a desire to use Cloud Workspaces to create a development environment on a VM where there is a k3d environment running.
What @kohlisid has in mind is that when somebody spins up one of these, it would deploy the Numaflow AddOn, and then deploy everything identical to that which is being deployed to other environments. While Cloud Workspaces does not require the "no data loss" features of Numaplane, the deployment through this means is seen as being more seamless.
There is no ArgoCD. One issue I can think of is that we no longer have the Sync Waves in that case. This would mean that a Pipeline can in fact be deployed without a corresponding isbsvc, and thus would enter a "Failed" state.
Perhaps, we could add a check before creating a Pipeline that the isbsvc exists and has been fully reconciled.
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: