kubefirst VS kind

this isn't just any typical friday for us though, this is the day that we've been awaiting forever!!! we're excited to announce that not only did we release a new awesome UI for the kubefirst instant gitops platform, and not only is it all still free and installs gitops platforms in minutes, and not only is it an incredible new user experience, but we even let you play our new video game flappy-kray during the cluster provisioning operation. 😱🚀🎮

[cofounder alert] Would love for you to consider our kubefirst instant gitops FOSS platforms. Fully managed K8S: our platform provisions managed kubernetes clusters in our cloud versions of the platform - or k3d clusters when running the platform locally Support for cross cloud and bare metal: we support aws, civo, vultr*, digitalocean*, and apply our k3d platform to bare metal stories, but our homelabs community is going in some neat new directions for bare metal k8s as well. Installation on new machines should be fully automatic: 100% - single command Terraform: all infra (terraform) and app config (argocd) is powered by a gitops repository that we give you, the tf is wired up and automated with atlantis, and your changes to the platform are a pull request away. love most of our tools, but hate a couple and want a bunch more - no problem, start here. --- stuff you didn't ask for: - application delivery with argo workflows preintegrated with github or gitlab with self hosted runners - secrets management, user management, and an oidc provider with hasicorp vault that's automatically configured throughout the platform. vault is our single source of truth for every secret throughout the platform (apps, iac, ci, etc) - cluster management: management of workload clusters (rancher like) will be release in 2.2 in a few weeks. we have to release our new ui first in 2.1 and that's expected in the next week or two. --- it seems like with the immediate cross cloud / hybrid needs you have, you may need more out of cluster management than we can offer today, but it's the focus for the next 2 releases. we're an open source free solution that's trying to solve a lot of the problems that you're up against, we have an active community and would love to help support your use case.

nothing blew up accidentally this week, but our team at kubefirst is falling more and more in love with aws-nuke. it's an open source command line tool that lets you basically reset an aws account back to an empty state. if you have an environment where you regularly practice your platform provisioning, you probably know that failed destroys while iterating on orchestration can leave junk behind pretty easily. aws-nuke has been so nice to be able to blow away everything in an aws account - and then we just run terraform in the account to get all our core infra back afterward. nice allowlist filters and dryrun detail work too. check them out.

we'll be looking into leveraging this technique at kubefirst - wondering if anyone here has other thoughts on the tech used in this piece or any FOSS alternatives we should be considering for container sig validation? this seems just about as frictionless as the discipline can get - but don't know what other gems might be out there in this space that folks may be flipping over.

at kubefirst we internally love both helm and kustomize. to build our instant oss gitops platforms we use both.

at kubefirst we build containers a lot - gitops ci pipelines are part of our instant oss platforms. i ran into this issue a few years ago that blew my mind and i haven't been able to reproduce until yesterday.

check us out if it sounds neat ⭐ https://github.com/kubefirst/kubefirst

Kubernetes: launch a service of your choosing, like Pritunl VPN. Dockerize it, create some helm charts for it, set it up in a CICD pipeline of your choosing. There's also a project called nebulous you might want to check out that aims to demonstrate k8s capabilities with a live env but it's very early stages. If you can do the former task in, say, DigitalOcean, you'll have a good head start. I can send you some additional "homework" you can work on if you'd like as well and the solution to the first task I mentioned just DM me.

To get started, you'll need to install clusteradm and kubectl and start up three Kubernetes clusters. To simplify cluster administration, this article starts up three kind clusters with the following names and purposes:

Kind: is a tool for running local Kubernetes clusters using Docker container "nodes." It was primarily designed for testing Kubernetes itself but can also be used for local development or continuous integration.

Fortunately, just as projects like kind and Minikube enable developers to spin up a local Kubernetes environment in no time, CRC, also known as OpenShift Local and a recursive acronym for "CRC - Runs Containers", offers developers a local OpenShift environment by means of a pre-configured VM similar to how Minikube works under the hood.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Features compared to https://kind.sigs.k8s.io/

Kind allows you to run a Kubernetes cluster inside Docker. This is incredibly useful for developing Helm charts, Operators, or even just testing out different k8s features in a safe way.

Check out KinD

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.

We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.

yes I know there is lens, but it does not allow me to see logs of multiple pods at same time and what is even more important it is not friendly for ephemeral clusters - in my case with help of kind I am recreating whole cluster each time from scratch