skaffold VS helm

K3d and Skaffold for local development

skaffold.dev - build in k8s - no more asking for the database password. All the plumbing to the backend is just done so it's easier for them to test and demo any branch

To access you service your have several options (it depends on teams the preferences) you can use scaffold https://skaffold.dev/ or for simple case kfwd https://github.com/GiGurra/kfwd. Last for everything that is normally expose on internet you would have an Ingress and use external-dns as you would in prod.

This approach works great when it’s feasible, which is usually at a very early stage in the life of the application where it’s still small and tenable. There’s some tooling that lets you extend this honeymoon phase by letting you do it more easily, like docker-compose, Skaffold, or Tilt. However, at a certain point, even if you’ve written whatever scriptage is needed to actually configure and run the latest stable version of all of your components together, you’re going to hit some sort of ceiling: if you’ve got a large database, or some CPU-heavy computations, or you’re relying on some managed service that can’t be containerized, this approach soon becomes untenable.

Another dev optimization is the conditional rebuilding of a container. For example tools like devspace and skaffold support syncing filles which have changes, but which don't require recompiling.

I have been using Skaffold to deploy my apps to Kubernetes. As I use this for spring Boot apps too so it saves me learning another deployment process.

I really like https://skaffold.dev/ for local development, speeds up repetitive commands I have to run like build/push/apply.

You might want to take a look at https://skaffold.dev/

Because these components are configured as Custom Resource Definitions on Kubernetes, you can create highly reusable pipelines, and Tekton is also compatible with Jenkins, Skaffold, Knative, and other CI/CD tools. Let’s take a look at getting started with Tekton, and start working on building our pipeline.

Lastly if you are using compose to both build and launch containers then you're going to need more advanced tooling like devspace or skaffold to assist in creating a better development workflow for kubernetes.

Kubernetes and Helm for deployment

What do you mean by stored? The notebooks are deployed on kubernetes using Helm https://helm.sh (1 notebook = 1 Helm release), their configs are stored as Secrets on Kubernetes. If you mean data inside the notebook, one can enable persistence (mount a PersistenVolume into the notebook) (via the Helm values, see https://github.com/machine424/notebook-on-kube#create-connect-to-and-delete-a-notebook).

Now here's the "gotcha"... you don't need to write Kubernetes manifest files to deploy your app. Instead, you will need to create another type of manifest file named Acornfile. This file is written in JSON-like syntax, feels very similar to a Docker Compose or Helm, and is used to package your application as an Acorn app.

https://helm.sh/ (a yaml based package manager used to tell k8s how to run your service)

Tools Official Links AWS CLI https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html eksctl https://eksctl.io/ helm https://helm.sh/

Spring web framework Spring WebFlux Reactive REST Services gRPC Java gRPC gRPC-Spring-Boot-Starter gRPC Spring Boot Starter Salesforce Reactive gRPC Salesforce Reactive gRPC Spring Data R2DBC a specification to integrate SQL databases using reactive drivers Zipkin open source, end-to-end distributed tracing Spring Cloud Sleuth autoconfiguration for distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Kubernetes automating deployment, scaling, and management of containerized applications Docker and docker-compose Helm The package manager for Kubernetes Flywaydb for migrations

You can automate everything from installation and upgrades to configuration management using simple APIs or declarative infrastructure as code (IaC). For deployment, you can choose from Helm charts, Kubernetes annotations, or Terraform.

ESO can be installed via Helm using the following commands:

For Kubernetes, experience with deploying applications with service resources is useful, but even if you don’t have this, this guide will walk you through it. Configuring KUBECONFIG to access the Kubernetes cluster with Kubernetes client (kubectl) and using Helm (helm), so familiarity to this is useful.

ShardingSphere-on-Cloud is capable of deploying and migrating ShardingSphere in a Kubernetes environment. With the help of AWS CloudFormation, Helm, Operator, and Terraform (coming soon) and other tools, it provides best practices with quick deployment, higher observability, security and migration, and high availability deployment in a cloud native environment.