Manage Docker and Kubernetes in VSCode
Vložit
- čas přidán 13. 06. 2024
- Discover how I revolutionized my HomeLab workflow by managing Docker and Kubernetes directly in VS Code! In this video, I dive into why VS Code, with its powerful extensions, has become my go-to for container management, offering simplicity and efficiency unmatched by other tools. #Docker #Kubernetes #TechTutorial
ARMO-*: www.armosec.io
Related Videos/Links
• The best VSCode extens...
• Using *HA* Kubernetes ...
________________
💜 Support me and become a Fan!
→ christianlempa.de/patreon
💬 Join our Community!
→ christianlempa.de/discord
👉 Follow me everywhere
→ christianlempa.de
________________
Read my Tech Documentation
christianlempa.de/docs
My Gear and Equipment-*
christianlempa.de/kit
________________
Timestamps:
00:00 Introduction
00:51 Advertisement-*
02:33 Why a code editor for container management?
05:32 Manage Remote Servers
08:30 Manage Docker Containers
12:40 Manage Kubernetes
________________
All links with “`*`” are and/or include affiliate links. - Věda a technologie
This new format of your channel since you returned is so good, really enjoying the content coming out, keep 'em coming 👍
Thank you so much! That is great feedback :)
I've been using vscode to manage my docker compose projects for 2 year now. The remote explorer extention is fantastic and, thanks to your video, I now understand how useful the docker extension can be. Thanks a lot Christian !
That is an awesome video, quite helpful and it really makes things easier
Glad it was helpful!
You always have great workflows, automations, and you really put time into continuous improvement and also showcase your knowledge! That's why I LOVE your channel! One question: How do you manage your homelab in terms of patch management? As I develop my own homelab, it becomes clear that just setting up services and forgetting about them in terms of upgrades/updates is not the smartest thing to do, but having a "dev" and "prod" environments for testing patches is a total overkill for my lab, which is a hobby (I don't want my hobby to become part time job; I already work in IT)
That's awesome. Great topics. Save me time... and made it easy now. Thanks!!
Happy to see you on the road again, Christian!
Thank you 😊
Great video! I knew about some of the docker extensions, but had no clue about all of the integrations it offered. Thanks!
Glad it was helpful!
Thanks Christian.
super useful tutorial, thank you so much 👍
Glad it was helpful!
As always good Video.
Great video showing alternative ways to manage servers and docker 👍
One big caveat of VS Code and Remote SSH extension is that the server site “client” uses a lot of memory. (110MB+) E.g. if you’re using a raspberry pi 3 or a cheap 1C 1GB VPS that’s over 10%, on a pi zero it’s over 20%. Just be aware of this, so you don’t produce out of memory exceptions.
Let's go VSCodium. :)
Well… it doesn’t support ssh remote as far as I can tell. So there is no way to use it as Christian is using it then.
no Microsoft extension works with VSCodium, and most of the Remote Development extensions are from Microsoft
great video! subscribed
Awesome, thank you! And welcome!
I also use VScode to manage my rapsberrypi!! Great tool!! Thank you for the video!! Cheers!!
Very cool! Thanks!
really usefull, relevant and pragmatic
why are not others talking more about this - I used vscode a lot and picked up things from this video so thanks for covering this so well
Thank you! :) Hope to cover those kind of topics more in the future
ich finde es auch witzig wie einem in anderen it bereichen immer gesagt wird man solle doch bitte eine ordentliche ide (jetbrains etc) benutzen, aber wenn man dann in die höheren bereiche kommt (cloud und ml) dann merkt man das alle devs dort vscode benutzen. jetbrains habe ich anfangs mal für react benutzt, aber es hat mich dann so genervt, das man die einstellung für das startverhalten beim debuggen nicht findet und selbst die leute im discord keine ahnung hatten wie man den port, start tasks etc anpassen kann, das ich es einfach nicht mehr benutzt habe. ist ja cool das es da so viele einstellungen gibt, aber wenn man den wald vor lauter bäumen nicht mehr sieht ist halt kacke. deswegen respect das du sagst: für jeden gibt es die richtigen tools
I use Docker extension a lot and is very helpful! For Kubernetes though I am using Lens which I find really great as tool as you basically have a general dashboard to see around what is going on in the cluster.
Lens is also great! I agree :)
Good video, I like the remote ssh connection to be able to edit files right on the server.
Thank you!
That's pretty cool.
Thx!
Thanks you!
You're welcome :)
Hi Christian, wonderful, engaging video as always. Would you mind a question? I see a wonderful library of docker compose and yml/yaml files. Do you sync those somehow across your different docker hosts (sorry if that’s the wrong word)? If so, what’s the best way of doing it? I’m guessing you might use GitHub somehow?
Why so small number of views? This is wunderbar video!
Thanks 🙏
Another good video. At the beginning I was using Mobo xtrem with notepad+. Now I use only use vscode.
Glad you enjoyed it
I've learned I could remote manage Docker which is awesome. just wish I couldn't figure out which of my 3 containers are messing up nextcloud.
Very very useful content...
What is the terminal at 14:10 are you using and which extension/plugin you install for autocomplete?
As always really awesome video, Christian!
I have a question, though: can you recommend alternatives to the microsoft extensions for those of us who want to avoid MS telemetrics by using VSCodium instead of VSCode?
Thanks! Hm not really, I mean why would you need alternatives?
@@christianlempa When using VSCodium you don't have access to those extension. :/
lovely and 🙏
Less is more!! Thanks Christian great video
Thanks :)
Hey @Christian -
Can you do a video showing us how Codacy works and how we can use this in a homelab environment. I see they have an OSS SaaS solution for code scanning
ich musste mich hinsichtlich kubernetes auch erstmal mit vscode zurechtfinden, aber was wirklich cool ist: secondary sidebar für kubernetes; dann kann man über sshfs die die volumes auf dem host mounten die man dann in vscode über multi root workspace einsehn kann. das ist aber auch jedesmal viel arbeit: docker starten, minikube starten, sshf verbindung herstellen, dann die ganzen ports forwarden usw in vscode. den ganzen anderen quatsch kann man dann ja in kubernetes dashboard machen (helm charts, übersicht über leistung etc). das ssh plugin kann man natürlich auch benutzen, aber irgendwie habe ich da noch nicht so den sinn für kubernetes gefunden. also ich mach aber auch alles auf einem rechner. also man kann mit minikube ja auch volumes vom host aus mounten, aber das muss eine 9p partition sein und das kriege ich auf rocky linux mal 0 hin, weil dieses epel release ding meine nvidia treiber nicht lädt
Cool for navigating and exploring but not for editing. Always use argocd and work from git to edit. And for secrets use sealed secrets.
Your videos are awesome
Nice tips, I like it. Have you tried this with docker-swarm?
Not yet!
Looking forward to trying those extensions but what really interests me is if I can split the VS Code screen and have my documentation on one side and the workflow on the other. Everything I am using at the same time in one screen!
You can open multiple VSCode windows, or you can split the editor into multiple windows. It's all possible.
Is there some vscode extension that can translate a yaml to a container graph?
I know it’s off topic but … almost cooler than Docker itself… what is the Matrix rain live background you have running on your Mac ??? Can you share details please…
And BTW… great video showing your workflow
Haha thanks :D It's just a simple "cmatrix" in my terminal ;)
Can you share the secret sauce ? I would love to have the same background on my studio
I am also using VSC but I got stopped on permissions: all my remote machines run dockers as root, ssh is only allowed for the user - not root of course. So when I use VSC I cannot manage remote containers not being root there. Rootless docker for some reasons is not really working there.
What can VS Code not do? I only recently started using it, and it looks like it will replace a whole bunch of my existing applications. Thanks for the great video, as always.
Thanks! Yeah VSCode is truely amazing :)
@@christianlempa Yes. VSCode does more and more things.
But it has a small problem and that is that it is getting heavier and heavier. I still remember when he appeared to overshadow Sublime Text.
We don't realize it because our computers are also becoming more and more powerful, but if you try to run VSCode on the same computer where you tried it for the first time... it's not the same anymore ;-)
has anyone run into issues with debian 12 docker container being unable to ssh into it with the plugin? this is the error i get "channel 3: open failed: administratively prohibited: open failed"
Great video. Can see you use 1 password for key managen. Hope will make video how to to integrate 1 password with vs code for remove access to servers. I can find any good videos about that. 🤞🏻
Thanks! I hope to make a comprehensive video about 1pass for devops at some point, but it's not a high priority on my list tbh
But why do you need VS code tool when you have the terminal?
I noticed on most of your video, you have auto suggestion in vscode editor or terminal. How can you do that?
In the Warp terminal, it's a built-in feature
The file extension doesn't matter in and of itself, but the defacto standard for defining Kubernetes resources is the yaml file extension, whereas the defacto standard for defining Compose files is the yml file extension. The Kubernetes Apply extension most likely just doesn't want to confuse the two (because both kubectl and docker-compose will work with both extensions) and thus only recognizes the yaml file extension.
Why do I say defacto standard? Because all the docs about Kubernetes mention the yaml extension, and all the docs about Compose mention the yml extension. Why is that? Docker was released in 2013, and Kubernetes was released in 2014. The Kubernetes team probably wanted to make a distinction here using the yaml file extension because everything about Compose was already using the yml file extension. If you will, Kubernetes Apply actually "adheres to the Kubernetes standard", so to speak. So nothing weird about that one, as long as you're aware of that small detail.
lol I have started to use VS code literally some 20 days ago to manage my docker hosts.
Awesome :D
Have you tried Dockage?
No yet but it's on my list for next year! :)
How closely related are you to Arnold Schwarzenegger?
😅
Relation: 1 octave removed
His is Arnold.