21–30 of 51 posts
Step out of the dark ages by burning piles of cash to generate light.
Earlier quoted context omitted.
Great work! I agree that developing in a Kubernetes namespace makes a ton of sense. This is also the direction we want to take the GitLab Web IDE. Kubernetes is the interface to the cloud, both for development, testing, and production.
Yes, the possibilities with this are very exciting. We have already integrated Gitlab runners in our Application Catalog, and we are working on a UX to deploy a branch and put it on dev mode on a single command.
Earlier quoted context omitted.
why? we offer vanilla kubernetes namespaces. There are no hidden dependencies
I believe they mean their application relies on third-party integrations that would be burdened by such a fast loop
Earlier quoted context omitted.
I develop in the cloud! Serverless Framework deploys are now less than three seconds. It's almost exactly like `run watch` now! I deploy to a dev AWS account, then a staging AWS account, and then promote to prod out of github. Check it out: https://github.com/serverless-components/
That really depends on the size of your app. You also lose the ability to run debuggers. Not to mention how hard is to run serverless java applications, which is the dominant enterprise programming language.
Github codespaces is a step forward to eliminate local setup and have replicable dev environments running in containers. But for true cloud-native applications, you would need a kubernetes namespace to run other services, databases or access the kubernetes API. This blog post explains our vision of cloud-native development at www.okteto.com
Great work! I agree that developing in a Kubernetes namespace makes a ton of sense. This is also the direction we want to take the GitLab Web IDE. Kubernetes is the interface to the cloud, both for development, testing, and production.
I'm really interesting in a cross platform, rootless and low overhead containerization solution for native desktop apps. I haven't seen one that fits my use cases yet.
Are kubernetes namespaces this well isolated? I wasn't aware it was at the point where you could put untrusted tenants next to each other in the same cluster.
I deal with a lot of "works on my machine" bugs, but the reason is we can't go cloud native. Or cloud. I'm really interesting in a cross platform, rootless and low overhead containerization solution for native desktop apps. I haven't seen one that fits my use cases yet.
Don't you tell me I'm living in "the dark ages" mister, I'm fully serverless. It's you who's grasping for a world soon to be gone.
How do you develop your functions? Using Kubernetes as a development platform also applies to serverless, we have articles with Cloud Run and OpenFaaS: https://www.openfaas.com/blog/painless-serverless-developmen... The idea is to have replicable and production-like dev environments, no matter your deployment tool
When ready, I merge into master, push, and they deploy to AWS through CI - I have simple Python scripts that manage Lambda Layer creation, environment variable configuration, etc.
Don't really need much more than this.