@Anais Urlichs Great Video, please comment the blog or make another video (if possible), for automating the whole CI/CD pipeline using Argo-events, workflows and Argo-cd.
Nice walkthrough! just a nitpick: you could update the name of the video to "Argo Workflows" only. Came here for Argo Events and left with empty hands :(
Heya, it is indeed WSL 2 with oh my zsh and starship, here is a video where I talk a little about my terminal setup ua-cam.com/video/slvQGMXau90/v-deo.html
@@AnaisUrlichs Sadly, I came here for the answer to the question that stumped you as well. I'm able to wire things up between events and workflows by deploying all of the CRDs and related manifests to one single namespace - in my case argo. If you notice on the Workflows UI, each of the services is being namespace-scoped to "argo". I think that's fundamentally the issue: how to cross namespace boundaries with the two - or whether to at all; either at the service account level or resource level. Alas, the search continues... I do find it confusing that the how-to and introduction for each respective tool ignores the notion of working together entirely 🤷♂
@@jasondeka5717 I got the following links from the community chat; have not looked at them yet but maybe they are helpful kccncna20.sched.com/event/ekGL/how-to-multiply-the-power-of-argo-projects-by-using-them-together-hong-wang-alexander-matyushentsev-intuit github.com/alexmt/argo-combined-demo
I don't know why your channel never showed up before but it's great. Thanks you
hahha well I am glad that you found it now :)
That was a great run through, thank you.
Thank you so much for the comment :)
great primer on the topic. thanks a lot!
thank you very helpful
@Anais Urlichs Great Video, please comment the blog or make another video (if possible), for automating the whole CI/CD pipeline using Argo-events, workflows and Argo-cd.
Nice walkthrough! just a nitpick: you could update the name of the video to "Argo Workflows" only. Came here for Argo Events and left with empty hands :(
thank you, I will do that. Sorry about that
@@AnaisUrlichs fyi, I kind of made it work, inspired by your work :) so thanks also to you for the motivation
excellent video. thanks. what is the Linux terminal used on Windows10? I know few like Subsystems, but please suggest best apps and linux terminals
Heya, it is indeed WSL 2 with oh my zsh and starship, here is a video where I talk a little about my terminal setup ua-cam.com/video/slvQGMXau90/v-deo.html
16:28
*burst out laughing*
am actually here cuz it's a bit of jyup jyup
i ve been stuck on it for like 3 days, i guess am not the only one xd
OH NO!! I hope you get it working! let me know, maybe someone in the community has an idea community.100daysofkubernetes.io/
@@AnaisUrlichs Sadly, I came here for the answer to the question that stumped you as well. I'm able to wire things up between events and workflows by deploying all of the CRDs and related manifests to one single namespace - in my case argo. If you notice on the Workflows UI, each of the services is being namespace-scoped to "argo". I think that's fundamentally the issue: how to cross namespace boundaries with the two - or whether to at all; either at the service account level or resource level. Alas, the search continues...
I do find it confusing that the how-to and introduction for each respective tool ignores the notion of working together entirely 🤷♂
@@jasondeka5717 I am following up in the Argo-workflows Slack channel, maybe there is someone who can help :)
@@jasondeka5717 I got the following links from the community chat; have not looked at them yet but maybe they are helpful
kccncna20.sched.com/event/ekGL/how-to-multiply-the-power-of-argo-projects-by-using-them-together-hong-wang-alexander-matyushentsev-intuit
github.com/alexmt/argo-combined-demo
You didn't discuss Argo Events.
I love you
too much irrelevant talk in the beginning - get to the point quickly!
It's not like you are paying me for it