For the last four years, anyone wanting to deploy the Ingress NGINX Controller for Kubernetes would find its official Helm chart nginx-ingress in the stable repository maintained by the Helm project. Those days are over. And not just for NGINX, the most popular Ingress Controller used as a reverse proxy and load balancer, but for all open-source K8s apps. With the advent of Helm 3, the Helm project is deprecating the stable repositories.

The growth of Kubernetes has been stellar and K8s applications have grown in importance and complexity. Today, even configuring a single application can require creating many interdependent K8s sources that each depend on writing a detailed YAML manifest file. With this in mind, Helm as a package manager for Kubernetes is a major way users can make their K8s configurations reusable.

Using an open-source Go module from the community of other developers can be like going on a blind date. That “getting to know you” phase that can be awkward and risky. The more you know in advance, the better off you’ll be, right? When using software, having accurate and precise documentation is one of the most important aspects. Good software documentation tells the story of what a particular piece of code does and how to use it.

Introducing, adding, or replacing a new SCA (Software Composition Analysis) tool such as JFrog Xray into your SDLC, if not handled correctly, can be very disruptive to the SDLC and organization. This blog post provides recommended best practices for onboarding JFrog Xray; in order to reduce disruption, improve adoption, and shift left to create a DevSecOps behaviour.

Jessica Deen’s swampUP 2020 talk takes Kubernetes to the next level. If you want to understand how to make your K8s implementation enterprise grade, then this is the session for you. JFrog was proud to announce Jessica Deen, Microsoft Azure Avenger, as the winner of the inaugural swampUP Carl Quinn Speaker Award. Jessica’s talk was full of demos, practical advice, and covered a wide range of real-world situations.

Adopting cloud native technologies like Kubernetes and Helm means your company’s operations can sail swiftly across the globe’s oceans to reach teams and customers. But there are dangers in the deep. With many components in Kubernetes, securing every dimension can be quite challenging and require a bit of learning curve. Let’s identify some important best practices that can help you to steer straight.

In their presentation at the swampUp 2020 conference, IT service manager Marija Kuester and her team at Siemens AG revealed how they use JFrog Artifactory to deploy and scale their Inner Source Hub service, and meet the challenging needs of their key business stakeholders. In the recorded session, the Siemens team outlined the service architecture with rich insights into the IT service deployment and internal developer adoption.

Feature branch workflows are used to isolate work done on a specific feature in a dedicated branch. This allows all development to be kept away from the team’s common codebase until completion. Essentially keeping the master safe from any risk until it is ready to be merged.

DevOps adoption is happening by the largest organizations across the globe. At JFrog swampUP 2020, Gal Marder, VP of DevOps Acceleration and Shimi Bandiel, solution architect of the DevOps Acceleration team at JFrog, spoke about the new challenges encountered by many of these large organizations practicing DevOps when it comes to Continuous Delivery in their CI/CD process.

If your Helm charts could talk, what would they say to potential users? Would they boast of the power in the Kubernetes apps they deploy? Would they warn of their dangers? Would they offer advice? In JFrog’s new ChartCenter, a community repository of publicly available Helm charts, that’s exactly what they’ll do. ChartCenter reveals to users what known risks lie within the container images deployed by every Helm chart.