kubernetes VS Juju

Kubernetes version 1.33 introduced several new features and bug fixes, and AWS is excited to announce that you can now use Amazon Elastic Kubernetes Service (EKS) and Amazon EKS Distro to run Kubernetes version 1.33. Starting today, you can create new EKS clusters using version 1.33 and upgrade existing clusters to version 1.33 using the EKS console, the eksctl command line interface, or through an infrastructure-as-code tool. Kubernetes version 1.33 includes stable support for sidecar containers, topology-aware routing and traffic distribution, and consideration of taints and tolerations when calculating pod topology spread constraints, ensuring that pods are distributed across different topologies according to their specified tolerance. This release also adds support for user namespaces within Linux pods, dynamic resource allocation for network interfaces, and in-place resource resizing for vertical scaling of pods. To learn more about the changes in Kubernetes version 1.33, see our documentation and the Kubernetes project release notes.

3. Kubernetes (kubernetes/kubernetes) – Container Orchestration at Scale

Self-Healing Pods/Containers: Platforms like Kubernetes inherently offer self-healing capabilities, automatically restarting or rescheduling unhealthy containers or pods to maintain desired service levels. This is fundamental to cloud-native resilience.

Kubernetes Kubernetes is a tool for orchestrating(managing) docker containers. With this tool you can deploy, scale and manage your containerized apps. Kubernetes commonly used in developing and production.

Global settings are easy to check and verify and modern frameworks handle it for you, because there's all these knobs. (I agree it's waaay too many, but that's because there's a runtime and on top of that there's a process manager, and on top of that there's nginx/apache or other reverse proxy.)

Sure, someone can write a Go library to wrap every low-level function to make sure there's some error handling, maybe with closures and generics it would be quite okay.

In Go if you don't see the error handled you know it's not handled anywhere else. Great? Well, sure .. um, maybe? After all if you want to handle it you need to add error handling there. Consequently your code now is 3x as many lines and ~66% of it is returning errors upward. It's the new Assembly.

(I don't think try-catch is good, I think that PHP's error handling is better despite try-catch.)

Porting to Go (for reliability or otherwise), why? There are other languages out there! Especially if you spent the last decade learning about compile-time checks.

I know that k8s (and tons of now-critical software) is written in Go, and it's not a pretty sight -- and instead of having better abstractions there's NASA-cargo-culting[0]. Linux is written in C. It does not make C a great choice for many reasons. (Go is definitely a better choice than C when it comes to memory safety for example, but I prefer Scala or Rust.)

Facebook added their own typing to PHP (and tellingly called it Hack, of course).

[0] https://github.com/kubernetes/kubernetes/blob/ec2e767e593953...

Kubernetes is a system for managing containers. It helps you run apps across many servers. It handles scaling, failover, and more. It’s used by big tech companies and is one of the most important cloud tools today. Written in Go.

Kubernetes + Pipeline CI/CD

Cloud-Native Friendly: Lightweight and fast, Go apps fit perfectly into containerized environments like Docker and Kubernetes.

Over the years, Indian developers have played increasingly vital roles in many international projects. From contributions to frameworks such as Kubernetes and Apache Hadoop to the emergence of homegrown platforms like OpenStack India, India has steadily carved out a global reputation as a powerhouse of open source talent.

I think it could be something like https://juju.is/ or https://www.systeminit.com/ but maybe I am not understanding what you mean.

Basically juju is used to deploy microservices, and other stuff too: https://juju.is/

Juju https://juju.is/

https://juju.is/

Each app is packaged in a charm which seems to be a yaml declaring inputs, dependencies and other meta data and optional python code that can respond to certain lifecycle hooks

https://discourse.charmhub.io/t/implementing-relations/1051

   name: my-node-app

I am currently working myself through setting up our new Research GPU-Cluster where we have "sort of" managed to deploy MAAS to manage all the servers more efficiently, and on top of MAAS then use Juju to deploy the further components of the cluster. The components here are

Kubernetes Custom Resources were created to allow the Kubernetes API to be extended for domain-specific logic, by defining new resource types and controllers. OSS frameworks like operator-sdk, kubebuilder and juju were created to simplify the creation of custom resources and their controllers. Tools built with these frameworks came to be known as Operators.

Depending on what you're trying to accomplish, Juju and MAAS, if not just automate with preseed for custom desktops.

At Canonical I work on two open-source projects written in Go: Juju, a large cloud-based application deployment tool, and Pebble, a small Linux service manager. Both include CLI clients and API-based server daemons. Juju in particular is a large distributed system.