The Red Hat Learning Community has a new design! This latest update includes new features and platform enhancements that continues to supplement and drive open source skill adoption for learners of all skill levels.
In the previous part of the series, we explored Open Policy Agent and implemented an ACL-based access control for our application. In this entry, I am going to share with you some of the discoveries that I made while evaluating Open Policy Agent in regards to policy design and development.
Recently I was looking for a way to implement access control for microservices. I needed a solution that would allow defining complex authorization rules that could be enforced across many services. After searching the web, I discovered a very promising Open Policy Agent project that seems to be the right tool for the job. In this series of three blog posts, I am going to introduce Open Policy Agent to you and highlight how it can help you.
By Mike Stephens, CEO of Entrepreneurial Spark.
I’m not a software engineer. I don’t know what a container, stack or kernel is, and I find even trying to describe an API a bit like trying to explain the offside rule. And until May 2016, I had never heard of “Open Source”.
Are you still doing all your Linux container management using an insecure, bloated daemon? Well, don’t feel bad. I was too until recently. Now I’m finding myself saying goodbye to my beloved Docker daemon, and saying hello to Buildah, Podman, and Skopeo. In this article, we’ll explore the exciting new world of rootless and daemon-less Linux container tools.
So many organizations are jumping on the Microservices bandwagon. The amount of hype makes the phenomenon nearly impossible to ignore. According to InfoQ, Microservices and their respective frameworks are in the “Late Majority” stage, meaning that even those industries and enterprises which are slow to adopt new tech are using them. That said, many of those same organizations are struggling to attain the promises that have been espoused by companies like Google or Twitter around Microservices.
This blog was originally published on Ales Nosek – The Software Practitioner.
Pods on Kubernetes are ephemeral and can be created and destroyed at any time. In order for Envoy to load balance the traffic across pods, Envoy needs to be able to track the IP addresses of the pods over time. In this blog post, I am going to show you how to leverage Envoy’s Strict DNS discovery in combination with a headless service in Kubernetes to accomplish this.
Network and Linux Administrators need to understand best practices and leveraging the advanced features of Ansible in order to enable scalable design and operation of the technology in the enterprise. This new training, Advanced Automation: Ansible Best Practices (DO447), expands on knowledge of best practices using Ansible skills that students were introduced to in Red Hat System Administration III: Linux Automation (RH294).