Operations | Monitoring | ITSM | DevOps | Cloud

Like every industry sector, 2020 has been a tough year in tech. The pandemic has changed the way we work, it’s changed the way our customers work, and it’s been a rollercoaster ride. In August 2020, IDC’s Global ICT Spending Forecast 2020 – 2023 predicted 2020 revenue in the sector would fall to $4.8 trillion compared to its original estimate of $5.2 trillion.

We get it, installing Artifactory and the JFrog DevOps Platform on Kubernetes can be daunting. As easy as we’ve sought to make it with our official JFrog installation Helm charts, there are a lot of decisions to be made. That’s meant to give you the widest possible choice for how to best fit your JFrog installation to your infrastructure. But choice can be overwhelming, too.

Kubernetes has become the de-facto standard for deploying microservices and containerized applications. Still, there is a learning curve for a developer to get familiar with Kubernetes concepts and objects, how to write and manage the required YAML files, etc. While there is undoubtedly value in learning these concepts and tasks, I believe there is even greater value in getting your applications deployed faster and spending more time on your application code than on infrastructure-related objects.

There is no doubt that organizations have a difficult task to address the current requirements for building and managing APIs, especially if they don’t use tools like API Management. APIs require up-to-date and strong documentation, increased security levels, comprehensive testing, routine versioning, and high-reliability to be appropriately utilized.

The way we all work fundamentally changed during 2020. The global pandemic has accelerated the pace of digital evolution for many businesses, while prompting others to pivot or change course completely. The response to the crisis will continue well into 2021, but as we edge closer to the end of the year, many organisations will already be thinking about the longer term impact of the pandemic and how to realign their business for growth.

Remote teams that work on dependent products face resource crunches and delays. When several teams work on interrelated projects, the chances are high that they will soon end up meeting at some point where they have to wait for resource release from another team or teams. For instance, when team A wants an update to an app currently maintained by Team B, they would want to automatically access the latest version of the app whenever a new bug is fixed and an update is made.

Route SSH connections through HAProxy using the SSH ProxyCommand feature and SNI. Did you know that you can proxy SSH connections through HAProxy and route based on hostname? The advantage is that you can relay all SSH traffic through one public-facing server instead of needing to grant users direct access to potentially hundreds of internal servers from outside the network.

Service Mesh is an emerging architecture pattern gaining traction today. Along with Kubernetes, Service Mesh can form a powerful platform which addresses the technical requirements that arise in a highly distributed environment typically found on a microservices cluster and/or service infrastructure. A Service Mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices.

Have you ever wanted to try K3s high availability cluster “mode,” and you either did not have the minimum three “spare nodes” or the time required to set up the same amount of VMs? Then you are in for a good treat: meet k3d! If you’re not familiar with k3d, its name gives you a hint to what it’s all about: K3s in Docker.