Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes is the world’s leading container orchestration platform. Its cloud agnostic status enables you to manage your workloads with ease, whether they reside in the cloud or on-premises. It has reduced the necessity of being locked into services provided by a cloud provider as well as the need for an entire operations team to manage large workloads on-premises on virtualization platforms.

Deployment controllers are a type of Pod controller in Kubernetes. They provide fine-grained control over how its pods are configured, how updates are performed, how many pods should run, and when pods should be terminated. There are many resources available for how to configure basic deployments, but it can be difficult to understand how each option impacts how rolling updates are performed.

Have you ever grown tired of running the same kubectl commands again and again? Well the good folks over at the Kubernetes team understand you. With the addition of custom resources and the operator pattern, you can now make use of extensions, or addons as I like to call them, to the Kubernetes API that help you manage applications and components. Operators follow Kubernetes principles including the control loop.

When requirements change for your product, there arises a need to change not only the codebase but also the existing data that already lives in production. If you’re performing the changes locally, the whole process seems fairly simple. You test your new feature against a sparkling clean database, the test suite is green, and the feature looks great. Then you deploy, and everything goes to hell because you forgot that production was in a slightly different state.

This weekend I had the opportunity to participate in the AWS Hackathon in Portland. Based on the hackathons hosted at re:Invent, this brought together about 100 developers of all skill levels to break up into small teams and produce a demo product in 10 hours. I had a great time, and wanted to share what I learned! There may be organization-specific roadblocks to adopting AWS Lambda right now and therefore, it might not be the right fit for your team at this particular juncture.

A rack is a structure, usually made out of metal and cabinet or wall-shaped, which allows to store and organize the different components of computer installations, such as servers, storage systems, switches, etc. Is that it? Are you disappointed? Well, hold on, although they don’t seem like much, the world of racks can actually be quite tricky.

Unity is strength. And at JFrog, we’re committed to providing the strongest DevOps tools available. With the promised release of the JFrog DevOps Platform, it’s my honor and delight to announce JFrog’s biggest leap yet toward fulfilling our universal vision of Liquid Software. We’re excited and proud to launch the world’s first universal, hybrid, end-to-end DevOps platform.