One of the common questions I get asked by developers is how they can use OpenShift locally for their own development. Luckily, we have a lot of different options and selecting one depends on the specific development environment that you prefer to work with.
I’ve catalogued the most common reasons Kubernetes Deployments fail, and I’m sharing my troubleshooting playbook with you! Without further ado, here are the 10 most common reasons Kubernetes Deployments fail:
The OpenShift Java S2I image, which allows you to automatically build and deploy your Java microservices, has just been released and is now publicly available.
Linkerd is the latest hosted project to join the CNCF alongside Kubernetes, Prometheus, OpenTracing and Fluentd. Linkerd is an open source, resilient service mesh for cloud-native applications.
I have been an aggressive Kubernetes evangelist over the last few years.
Here at New Relic, DevOps is an integral part of how we operate—different teams collaborating to help foster more frequent deploys, faster issue resolution, and more stability and innovation across the organization.
When it comes to software development, a majority of the tools available to us are command-line applications. It is also well worth noting that many of the tools used on the command line are quite powerful in what they can accomplish, from the trivial to the tedious.