Видео

Profound knowledge on the topic, thank you. Very impressive.

Cilium Hubble's great (another reason for replacing kube-proxy)

I watched your tailscale, microk8s and raspberry pi video a little over a year ago. It inspired me to go down every rabbit hole Kubernetes has to offer! Your content is still peak technical and im thrilled to see youre back posting! Is there a CloudNativeSkunkworks slack or discord we could join? Id be thrilled if you chose to make content on any of the following: -Your take on using kube-vip -A refreshed take on ArgoCD "app of apps" design patterns. - High availability cluster tips. - Running Ceph in a cluster and using PVCs with it

Welcome back! more advanced cloud content like building k8s operators pleaaase!

Thank you so much!!

Very nice and informative video to get started. I guess you have covered the basics right well. Most of the other articles haven't really been easy to follow. Keep up the good work.

Changing OpenStack rabbit MQ to some other more stable queue

Talos linux, nix os, bare metal k8s in general...

Will true/hard multi tenancy ever be achieved in kube natively? On the one hard you need microvms, confidential containers, trusted enclaves, apparmor, etc. All hard and flaky. Then from developer perspective we still cant let them have access to only the logs, metrics, events, traces, etc that is relevant to their tenant/namespace only. Isnt the promise that what they build they operate, but we cant give them what they need?

Building k8 operators, controller. Interacting with k8 API from inside Kubernetes.

Idea: How to setup on prem Omni/OpenStack to create on demand clusters with Cluster API/Crossplane or Omni API, or running OpenStack on Omni to abstrack even further... If that is done, how to properly manage a lot of clusters decleratively with Argo CD with ESO and Vault/OpenBao. Where to put Helm charts, how to manage those, or are there better alternatives? How to handle environment progression for artifacts, like promote versions from dev -> staging -> prod. How to test things (if you have a single argo instance on an infra cluster for example), too make sure not everything goes black after you bumb the argo version... :D How to setup good tracing How to really use pod replicas Permissions, security, ... I guess there's no end

Leave a comment and let me know what you want to see us cover

this is really different from what i thought about microservice, i think this is just monolithic project

You GOTTA see the 9320!!!!!!!!

great video.

Amazing video to get started with the cobra library. Thank you so so much.

You reckon I could use this laptop for video editing thinking of getting one

Thanks for the examples in the terminal, otherwise it would be a ordinary lecture

great video

You didn't really have to lift your laptop all the way up to show what M1 or M2 laptops are :D

Justin Timberlake?

Thanks a lot 👍

Great video, hope you return to RUclips

Wow, someone actually managed to explain Generics and Generic Functions in a way that makes them simple to use. One thing to be added: How to make user defined types valid constraints by simply prefixing their underlying primitive type with ~, so that e.g. 'type MyInt int' becomes a valid contraint via ~int.

Good one, but I meet a issue here is. I bootstrap the applications using the kubectl, but when I delete it using kubectl, only delete the bootstrap applications, other child applications will keep. But when I try delete them in the argocd UI. All the child resources gone. Do know why, do you have any thoughts or insights?

Excellent short crisp and valuable content.

Why would anyone care about how cgroups work? Just to sound smart. 🤣🤣

Gemini 1.5 Pro: This video is about container technologies including cgroups, runc, and containerd. The video starts with explaining cgroups. Cgroups are a feature of the Linux kernel that allows you to allocate and manage system resources. It allows you to create control groups that can be used to limit the amount of CPU, memory, disk I/O, network bandwidth, and other resources that a process can use. Cgroups can be used to ensure that critical services have the resources they need to run, and to prevent runaway processes from consuming all of the available resources on a system. Next, the video covers runc. Runc is a reference implementation of a container runtime. It is used to create and manage containers. A container is a standardized unit of software that packages up code and all its dependencies so that it can run reliably on any Linux system. Runc provides a way to create containers that are isolated from the host system and from other containers. The last topic covered in the video is containerd. Containerd is a container runtime daemon. It is used to manage the lifecycle of containers. This includes downloading container images, creating containers, starting containers, stopping containers, and deleting containers. Containerd works with runc to create and manage containers. In summary, cgroups provide a way to allocate and manage system resources, runc is a tool that can be used to create and manage containers, and containerd is a daemon that is used to manage the lifecycle of containers. These technologies all work together to enable containerization.

Well, it’s looking interesting, but I have a few questions. What does with provided clusters if I delete control cluster? How I can manage control cluster, such as upgrading? Which upgrading workflow could I use for my clusters? How I could migrate my clusters to new control cluster?

I'd love to use Kubeshark but their payment model kinda makes it not possible. Free model only accounts for 2 node clusters, which in todays age, is pretty much unrealistic.

Can you please create a realtime kubernetes operator may be aws dynamodb kubernetes operator, that manages dynamodb

Love the cluster case I need info

undoubtedly, your setup is brilliant 👏

Thanks for sharing! How code is automatically generated at 15:06？

Looks like there's an error on line 65 let obs = watcher(topologys, ListParams::default()).applied_objects(); You cannot receive Node updates by watching a Topology resource. The correct one might be: let obs = watcher(nodes, ListParams::default()).applied_objects();

What OS was running on the Kubernetes nodes on AWS EC2 instances? Great video, thank you.

Did they make a 4k version or was this a mod?

Great video, thank you. Just curious about which console editor or plugin is used, seems very nice.

There is no "diaspora of implementation." There is a variety of implementations. "Diaspora" always refers to groups of people who share a common homeland. The rest of the video was helpful.

How can i use Kubeshark in eks cluster?

This is really good. Thanks for this video

Thanks for the wonderful explanation of k8sgpt capabilites. I tried it with Azure OpenAI as the backend and it worked very well. Looking forward to the future improvements and enahncements which will make this a good handy tool in the hands of SRE and DevOps engineers. Great stuff.

i have the exact same one

Yum! 💀

Thank you so much. It is very helpful for me. Could you explain in which case should we use kubebuilder and in which case operator-sdk?

Didn't know that Justin Timberlake was into kubernetes

amazing explanation and a great video. Thank you.

This is an excellent walkthrough not an artificial isolated example, but how one would actually structure Cobra-based project.

Thanks for the great video, found it from your Reddit post. I’m currently managing 20 EKS clusters with Terraform and going to give this a try.

I find your video very helpful, but I have a question: some tutorials use the following ways to set variables: `inputs = {...`} `locals {...}` `variable "my_var" {...}` Some we import with a `read_terragrunt_config(...)` others seem to auto load, It seems there are a lot of ways to set and pass around variables, what are the differences and when should I choose one over the other?