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
i am trying to use "kubespay" (great tool btw :heart) - to watch multiple deployments.
having the following questions.
kubespy trace deploy krn-dev/api
[ADDED extensions/v1beta1/Deployment] krn-dev/api
Rolling out Deployment revision 4
✅ Deployment is currently available
✅ Rollout successful: new ReplicaSet marked 'available'
ROLLOUT STATUS:
- [Current rollout | Revision 4] [ADDED] krn-dev/api-7578c97964
✅ ReplicaSet is available [1 Pods available of a 1 minimum]
- [Ready] api-7578c97964-8glps
i'd like to start multiple threads and run one kubespy per deployment.
kubespy should exit once deployment status is ✅
resulting in the thread to quit, once all threads are gone, i can be sure my deploymentS are done.
is there already a option for that scenario?
if not, can you guide me to the direction where to start, i would love to contribute.
The text was updated successfully, but these errors were encountered:
Hi @hjanuschka, thanks for checking out Kubespy! It doesn't currently support the scenario you mention, but you might be interested in our Kubernetes provider for Pulumi. It's based on the same tech, and is purpose-built for scenarios like that. No more struggling to figure out if your Deployments are ready! (We built Kubespy while developing the readiness logic that powers the provider).
i am trying to use "kubespay" (great tool btw :heart) - to watch multiple deployments.
having the following questions.
i'd like to start multiple threads and run one kubespy per deployment.
kubespy should exit once deployment status is ✅
resulting in the thread to quit, once all threads are gone, i can be sure my deploymentS are done.
is there already a option for that scenario?
if not, can you guide me to the direction where to start, i would love to contribute.
The text was updated successfully, but these errors were encountered: