awesome-mlops VS kind

I'm in the same boat. Data scientist shifting towards ML engineering-MLOps. The guide seems quite complete. I am also doing the ML DevOps engineer, which has end-to-end projects and has been helpful so far. I also feel that most ML engineers will be Mlops too, as most companies will not distinguish between the two, so I try to focus on this part. Here is a quite comprehensive list of resources: https://github.com/visenger/awesome-mlops

Good Reference: https://github.com/visenger/awesome-mlops (The Link above has so many Guides, It's insane) https://madewithml.com/

I recently did a deep-dive into MLOps for a client, and I've found that https://ml-ops.org/ offers a great overview. Some topics are a bit too "zoomed out", but they still touch on most important aspects of building an end-to-end product. I found it a great starting point when doing research, and picking and choosing some key points from each section + some google helped a lot. Give it a look, you'll probably find some useful things in there.

MLOps

She made mentions to ML-Ops and MLFlow including Vertex AI the GCP implementation. I will post the video as soon as it is available. In the meantime, you can enjoy any other talk from Nerea Luis

From your post, you seem to be trained for data science for physics modeling, so I'd recommend to get started with https://ml-ops.org/ and for the data engineering part, I found this https://github.com/andkret/Cookbook open source cookbook to be invaluable.

Have you tried https://kind.sigs.k8s.io/? If so, how does it compare to k3s for testing?

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.