helm-charts VS okteto

Helm installed on your machine. The Elastic modules will be installed using the official Elastic Helm repo. Although the repo is now read-only, it is still fully functional, and the community is expected to maintain it.

The Elastic Stack is our Swiss Army Knife on the cluster. The whole Elastic Stack has been installed in version 8.5.1 inside the cluster. We know it's not recommended to have stateful apps in Kubernetes, but we are in the early stage of our production.

Hi, I am looking to load the default dashboards that come pre-built in Kibana by setting up a Kibana endpoint in metricbeat configuration. The "setup.kibana" option is not really available in the official metricbeat helm charts as a setting (https://github.com/elastic/helm-charts/blob/main/metricbeat/values.yaml). The option to setup a kibana endpoint is only available in the regular metricbeat.yml file which we generally use in a VM based deployment. (https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-reference-yml.html).

apiVersion: networking.k8s.io/v1 kind: Ingress #https://kubernetes.io/docs/concepts/services-networking/ingress/ metadata: name: quickstart-es-http-ingress annotations: # nginx.ingress.kubernetes.io/rewrite-target: / #https://github.com/elastic/helm-charts/issues/779 https://stackoverflow.com/questions/68893838/ingress-for-eck-elasticsearch-not-working-502-gateway #kubernetes.io/ingress.class: nginx #think this is wrong for our class? kubernetes.io/tls-acme: "true" #nginx.ingress.kubernetes.io/proxy-ssl-secret: "resources/elastic-certificate-pem" #=> need to point to ES certificate pem. nginx.ingress.kubernetes.io/proxy-ssl-verify: "false" #=> must be false if you use elasticsearch-utils to generate CA. nginx.ingress.kubernetes.io/backend-protocol: "HTTPS" #=> must be HTTPS <- this one fixed it. spec: ingressClassName: public rules: - http: paths: - path: / pathType: Prefix backend: service: name: quickstart-es-http port: number: 9200

Unfortunately the new security system introduced by ES 8.0 has produced problems with the official helm chart, so we cannot use the standard Okteto Chart deploy system. In this article we will see how deploy ES 8.x into kubernetes (k8s) using the Okteto Cloud as platform.

This might help you, you'd need to run this separately from the operator: https://github.com/elastic/helm-charts/blob/main/logstash/ Before embarking on a logstash journey you may want to check if beats (or agent) combined with Elasticsearch ingestion pipelines can meet your needs

We will deploy the Elasticsearch and Kibana using the official Helm charts which can be found here(Elasticsearch, Kibana). For installing via Helm you would need a helm binary on your path but installation of Helm is outside the scope of this post.

They have the repo with their helm charts published on github. Here's the values.yaml for elastic. The other apps (kibana, filebeat, etc) are in adjacent folders. The values you see in these files are the defaults.

Looks like they have recently changed node.roles https://github.com/elastic/helm-charts/pull/1186

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

Check also devspace.sh and okteto.com

You can consider using okteto for development environments, it lets you deploy your local code directly to k8s replacing the existing pods, our team uses it and it works pretty well with Golang.

Okteto is an application that allows you to develop inside a container, along with many features it permit the user to start a development environment and provide an automatic SSL Endpoints for k8s.

With Infrastructure as Code at its current state of maturity, it’s now easier than ever to replicate microservice environments in the cloud. This unlocked a new approach of having a personal production-like cloud environment for every developer, which they can use freely and in isolation. It comes in two flavors - persistent environments, or ephemeral environments created on demand with products like Okteto or Bunnyshell (also sometimes called Environment as a Service)1. This approach overcomes the resource limitations of the local environment but substitutes them for some new difficulties:

Remote development will be popular? Yes.

But developing in a monolithic machine may be not. The development environment should be clean and isolated, and products like gitpod and coder is promising.

Besides this, maybe you can have a look at https://github.com/tensorchord/envd and https://github.com/okteto/okteto

Okteto accelerates the development workflow of Kubernetes applications. You write your code locally and okteto detects the changes and instantly updates your Kubernetes applications.

Hey! Recently, I’ve been playing around with [Okteto](https://www.okteto.com/) to see how it helps with the local development of apps that will run in Kubernetes. It seems to be quite a good option for developers who don’t want to spend their time dealing with setting up and maintaining clusters. Moreover, you can use a development environment from Okteto without thinking about CI/CD pipelines for delivering the app.So, instead of working on your code locally and deploying it then to the cluster, the whole development process is shifted straight to K8s. That makes Okteto approach a bit different from what other projects, like Skaffold and werf, do. To implement this idea, they offer a [CLI tool](https://github.com/okteto/okteto) and their own cloud provided as both SaaS and self-hosted (it has a limited free option).Here is [my overview](https://blog.flant.com/okteto-cloud-for-local-development-in-kubernetes/) of Okteto; any feedback — especially, your own experience — is more than welcome.

There's a long long route to cloudification, but works like Okteto[1] seem like a nice early pass at doing what Docker-Compose was capable of for fast local development, but modern. Pursuing remote-development makes a lot of sense. There's already solid VSCode integration[2].

If you just need a terminal like thing to local-dev in, toolbx[3] is probably the first choice.

[1] https://github.com/okteto/okteto

[2] https://marketplace.visualstudio.com/items?itemName=okteto.r...

[3] https://containertoolbx.org/

Hi Jacob. I am one of the founders of Okteto (https://okteto.com/), a remote development platform for Compose and Kubernetes applications. We use Syncthing to sync code between the developer laptop and pods running in Kubernetes. I would love to know your thoughts on the strengths and weak points of Mutagen vs Syncthing for this use case.