You’ll start by building the code of the application, then we’ll define the application with Okteto Stacks, and finally you will deploy it to Okteto Cloud.
As a developer, there’s going to be a time where you need to work with different Kubernetes clusters. At a minimum, you need to work with two clusters: one is your local cluster, and a second one could be a remote cluster for testing purposes in a cloud provider or elsewhere. Kubernetes has contexts, a set of configurations you can use to interact with different clusters from your workstation using kubectl. At the end of the day, remember that you’re interacting with an API to persist the desired state for your workloads.
Even though kubectl offers a set of commands you could use to work with different clusters, you might need another set of tools to make your life easier. Sometimes, typing long commands would decrease your productivity, and they’re hard to remember initially. And if you’re using okteto, you don’t need to use another tool and almost forget about kubectl to work with different clusters. We’ll see in this post how’s that possible.
Chaos Engineering is a key practice of Cloud Native Development. You can’t really guarantee that your Cloud Native Applications are “distributed and resilient by design” if you don’t know what’s going to happen to then when something fails in production.
Join Sylvain Hellegouarch (CTO at ChaosIQ), Kristin Barkardottir (SRE at NetApp), Sumit Nagal (Principal Engineer at Intuit), Karthik (Core maintainer of LitmusChaos), Divya Mohan (Enterprise Engineer at HSBC) and I as we talk about the need for Cloud Native Chaos Engineering, the benefits of this type of practice, and strategies on how to get your company to invest in a Chaos Engineering practice. I learned a lot, and I hope you too!
Interested in getting started with Cloud Native Chaos Engineering? Check out how to get started on Chaos Engineering with Litmus and Okteto. And if you’re in KubeCon NA next week, don’t miss Sumit’s talk on how Inuit uses LitmusChaos to manage and orchestrate their chaos experiments.
See you online!
Without any doubt, Kubernetes has become the default platform to run modern applications. However, for a developer, working with Kubernetes brings a new set of challenges, and a learning curve that might be intimidating. Additionally, and more importantly, the development inner loop now requires a few more steps before you can test your app.
To put this in perspective, prior to Kubernetes, the inner loop for Rustaceans used to look something like this:
cargo run(which includes compiling)
And when you add Kubernetes to the formula, the inner loop looks like this:
These extra steps from above easily translate into a minimum of two minutes. If you want to fix something quickly, those extra steps become an eternity. There has to be a better way, right? Yes, there is, and the answer is Okteto.
Last week, Adam and Craig interviewed me on the Kubernetes Podcast from Google. It was a very fun interview where we talked about the origin of the company, the state of the Kubernetes development experience, what was it like to go through YCombinator’s demo day, and many more things.
If you always wondered why Okteto is named Okteto, who is Cindy Lopez, or where to get a burrito in San Francisco, this is the podcast episode for you!
If you’re interested in the Cloud Native space, I highly recommend you subscribe to it. Every episode I’ve listened to has been great so far.
What do you think about the interview? Do you agree with my 🌯 taste? Let us know over at twitter!
If you prefer reading the interview, a full transcript of the interview is also available on their site.
Developer Experience is not just about the tools and technologies you and your team pick. It’s also about the people in your organizations. In this post, Artur Meyster, founder of Career Karma, writes about how to stay relevant as an employee in the future of work.
With the recent Covid-19 pandemic disrupting every industry around the world, not to mention the disruption caused by advancing technology, it can be easy for any employee to wonder how they will fit into the future of work. At the end of the day, traditional jobs will see a decline in favor of those that are tech-based.
The recent onset of remote work has shown many companies how many of their jobs weren’t exactly necessary for success. In fact, The Washington Post discussed how over 20 million jobs were shed from company payrolls in April alone. Therefore, determining if your skills are relevant to your employers now and in the future of work is important to ensuring the longevity and success of your career. Below are a few of the best ways to ensure that your skills do indeed stay relevant in the uncertain future.
Join me and Saiyam (CNCF Ambassador and Director of Evangelism at Civo Cloud for a live coding session this Friday 23rd at 9AM PST / 9:30PM IST.
In this live coding session we’ll be talking about:
Grab some coffee ☕, fire up your IDE, and see you online this Friday! 🌐
Hacktoberfest is a month-long celebration of open source software. Each October, open source maintainers give new contributors extra attention as they guide developers through their first pull requests on GitHub.
This year, we’ve partnered with our friends in the LitmusChaos project to organize a global meetup to celebrate Hacktoberfest, and the LitmusChaos and Okteto open source projects.
And to help you get started, we are running our first ever promo: Sign up for Okteto Cloud with this link, and get two months of Okteto Developer Pro for free!
Come celebrate with us this October 17th. You might even win some Okteto and Litmus swag 😉.