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.
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();
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.
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 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?
did the unset not work because you unset NAME rather than TOOLBOX_NAME with the defined prefix? Great video. Just getting started with viper this saved hours
On my setup the save button doesn’t show up.. something else kubeshark didn’t detect the ZMQ traffic so I am wondering if the pcap file would contain any and loading it in wireshark would help
7 месяцев назад
"Some stl files i found" wow nice way to not give credit to the designer of the recovery kit, you didn't do shit but rip it off.
can it analyze historical changes to manifests (or api sequences for all native and CRs) since cluster bootstrap and predict how changes affected resource utilization ? like: ingest and compare all known best practice designs and find ways to better optimize for cost and performance? how do you plug into local bare metal ai ?
Unmanaged update/upgrades, many years of experience has seen major downtime trying to find what went wrong and even 10 years ago backups was left to the "It will never happen to me" mentality or experience , But that is only me. But in my lab, nobody goes home until the job is done.
