Cloud-based development environments are getting a lot of traction due to its great benefits: instant onboarding, access to cloud infrastructure with no friction, and easier team collaboration. I love the idea of clicking a button and have a ready to go development environment in seconds. This is the future of software development.
But cloud-based development environments come with a few of severe limitations:
It don’t have access to the underlying infrastructure.
I had a lot of great conversations after that talk. In one of those, someone asked me if okteto could also work the same way with Kubeless. I wasn’t familiar with Kubeless at the time, but I remember saying that as long as Kubeless “spoke Kubernetes”, it should work. Someone reminded me of that conversation the other day, so I decided to try it out. And, spoiler alert, it does!
In this post, we’ll talk about how to install Kubeless in your cluster, we’ll deploy our first function, and then we’ll use okteto to quickly iterate on a a second version of the function directly in our Kubernetes cluster.
Crossplane, for those of you unfamiliar with it, is an open source Kubernetes add-on that supercharges your Kubernetes clusters enabling you to provision and manage infrastructure, services, and applications from kubectl.
In the past, we’ve talked about how to develop remotely with VS Code. Today, I’m going show you how can you use okteto to define and deploy a fully configured remote development environment for your python application, how to integrate it with Jetbrains’ PyCharm and how to use it to build a Cloud Native application.
The Okteto Developer platform allows you to spin up an entire development environment in Kubernetes with one click. This can be as simple as a single container or as complex as a microservice-based Cloud Native Application. You deploy your application with one click, select the component you’re going to develop on, and you’re ready to go in seconds.
This week, we were part of OSCONF Bangalore 2020, and online conference on Open Source and Cloud Native Technologies. The conference was organized by our friends Ajeet, Saiyam and Sangamfrom Collabnix, with the help of the Okteto, Docker, Rancher and InfluxDB meetups in Bangalore.
The event was a lot of fun. The talks were all by practioners, and covered topics such as Serverless, Prometheus, KubeMQ, Redis, Istio, InfluxDB, Traefik and of course, Okteto 😎. It was a lot of fun, and I learned a lot.
You can build your React frontend locally. The local development experience is one of the best there is. But is very likely that, in production, your React frontend is going to to work along with other services, like a backend, or a database. What are you going to do then? Typically you’d end up mocking the backend, or calling a staging version, rendering your local development environments very complex…
In this post I’ll show how you can take advantage of the different features of Okteto Cloud to make it easier than ever to build a React application. You can still benefit from React’s local development experience, but you’ll also have access to a fully integrated, production-like development environment, backend included. Hello okteto up, goodbye production-only bugs 👋🏼!
This week, we were part of the AllTheTalks.online conference, a 23.9999 hour online-only conference on all things DevOps, Development & Security. And, as an added bonus, doubled as a fundraiser for COVID19 victims. Pretty cool no?
We talked about Okteto and how to use it to simplify the development of Cloud Native applications. The talked covered the history of the project, community use cases and a demo of how to find and fix a bug on micro services-based app directly in Kubernetes. It was a lot of fun!
Jeevanjot has been using Okteto Cloud for a while, but he really missed having a mobile experience. So he took matters into his own hands, started inspecting the different API calls that Okteto Cloud makes, and worked his way. And now, he’s ready to share his creation with the world.