hull VS kubernetes

If you are just starting out and decide to go with writing your own Helm Charts I'd like to suggest our HULL Helm Library Chart for that purpose.

With HULL we have proposed an alternative yet Helm based solution a year ago which that tries to do it upside down by first giving you a documented Kubernetes API style full access to each objects configuration. Only on top of that it provides you further advanced options to (re)introduce abstraction into the mix - only if you need them and they actually improve your configuration. Everything takes place in the values.yaml so there is no digging around in the templates folder and everything is in view.

The HULL library Helm chart provides a single common interface to specifying Kubernetes objects within Helm Charts. The interface itself is based on the Kubernetes API schema itself which is integrated as a JSON schema in the HULL chart. Since all objects are defined directly in the values.yaml under the hull key there is no need to create and maintain custom template files when creating objects with HULL, everything happens in the values.yaml.

Good, now proceed by creating a new empty HULL based Helm chart. The steps are documented here but you will create it from scratch here to understand what is needed.

As a reminder, the goal of this tutorial series is to demonstrate how to build Helm charts based on the HULL library chart by recreating the functionality of the original kubernetes-dashboard Helm chart with a HULL based chart from scratch. When you have followed the previous part of this tutorial on setting up a HULL base chart you have created a for now unconfigured Helm chart named kubernetes-dashboard-hull in the 02_setup subfolder of your working directory (we assume that's ~/kubernetes-dashboard-hull here). You can alternatively download the current chart state here and continue from there. Also you should have checked out and extracted the kubernetes-dashboard Helm chart to kubernetes-dashboard in your working directory because examining it will be frequently required.

the ability to specify any CustomResource as a customresource object instance. For CustomResources you additionally need to specify the kind and apiVersion besides the free form spec of your object.

We have built a Helm Library chart named HULL, it provides amongst other features full access to all defined objects and their properties at creation and deployment time. Think of it as an API to specify Kubernetes objects directly in a Helm charts values.yaml. If there is some functionality you want to add or use in a particular scenario you can just configure it and the Kubernetes objects are as you actually want them to be - every aspect can always be tuned at deploy time if needed without you having to get back to the chart creator via PRs, hack the chart or similar methods. All doable with Helm and the HULL library chart, no other tooling required!

We actually proposed an alternative way to solve the problem if you are Helm with our Helm library chart HULL.

It may be worthwhile to look at the recently added examles, these are more advanced chart values.yamls from products we are deploying this way. You can see it can be pretty concise to define your applications structure with HULL in comparison.

Downsides to this is that you would have to write out the full content of your config in the values.yaml and cannot use the templating capabilities any further. Within the values.yaml no templating is allowed (unless you base your chart on this library chart we have created ;) which may be a more advanced topic if you just got started)

In the field of software development, efficiency and agility are always sought after. In the era of cloud-native apps, traditional deployment techniques—which are frequently laborious and prone to errors—are starting to become obstacles. This is when Kubernetes and GitOps come in handy.

Are you looking for a hassle-free way to deploy Moodle™ Learning Management Systems (LMS) on Kubernetes? Look no further! Krestomatio presents the LMS Moodle Operator, an open-source Kubernetes Operator designed to simplify the deployment and management of Moodle instances on Kubernetes clusters. Let's dive into what makes this tool a great choice for Moodle administrators and developers alike.

Securing access to your Kubernetes clusters is crucial as inadequate security measures can lead to unauthorized access and potential data breaches. However, navigating the complexities of Kubernetes access security, especially when setting up strong authentication, authorization, and network policies, can be challenging.

Deploying AI models into production requires tools that can package applications and manage them at scale. Docker simplifies the deployment of AI applications by containerizing them, ensuring that the application runs smoothly in any environment. Kubernetes, an orchestration system for Docker containers, allows for the automated deployment, scaling, and management of containerized applications, essential for AI applications that need to scale across multiple servers or cloud environments.

To learn more, you can start by exploring the official Kubernetes documentation.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

We closely monitor Kubernetes and cloud providers' updates by following official changelogsand using RSS feeds, allowing us to anticipate potential issues and adapt our infrastructure proactively.

"You are holding it wrong", huh?

From the homepage https://kubernetes.io/:

"Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications."

Do you see "not recommended for smaller-scale applications" anywhere? Including on the entire home page? Looking for "small", "big" and "large" also yields nothing.