Abhinav Mishra | Rafay
Abhinav Mishra
Introducing Rafay Plugins for Backstage Self-Service
Today, I am pleased to announce the launch of the Rafay Plugins for Backstage, which will be generally available in the 2nd half of this year. For those who are unfamiliar with Backstage, it is an open source project by Spotify that enables platform engineering teams to build out internal developer portals (IDPs) as a means to enable developer self-service and significantly reduce cognitive load and burden that developers face today.
Rafay’s new Environment Manager Enables Developer Self-Service For Modern App Deployments - From Code To Cloud
Today, I am pleased to pre-announce the launch of Rafay Environment Manager, which will be generally available in the 2nd half of this year. Environment Manager is a new, cutting-edge service that provides platform teams with the management, governance, and automation capabilities needed to enable developer self-service for full-stack environment provisioning.
Seamless Landing Zone For Our Docs
These past few months, we've invested a lot of time as a team working to create a more seamless experience for our customer-facing product documentation . While we built a lot of content covering key functionality of the platform, one of the key questions that would arise from our readers was how do I know where to start?
How to Deploy Backstage in Kubernetes With Enterprise-Grade Governance and Automation
With Rafay, you can easily set up open-source Backstage as a means of enabling internal developer platforms and developer self-service on any type of Kubernetes cluster in the following categories: Product Blog Backstage Developer Self-Service Introduction To Backstage Recently, I published a ' recipe for Backstage ', an open-source project by Spotify that over the last year has witnessed tremendous adoption and growth by platform engineering teams of all types of enterprises. Some of the key features of Backstage include: An easy-to-use interface for developers Extensible plugin ecosystem (for ex.
Streamline Network Security with Centralized and Automated Network Policy Management
In a previous blog post, Securing Your Kubernetes Environments via Network Policies , we alluded to the value that network policies bring to Kubernetes environments in terms of isolation and reducing the lateral attack surface area, while also articulating some of the challenges around operationalizing network policies. To summarize, these challenges include the following: Integration and standardization of network policies : The operational burden in defining and enforcing network policies across a heterogeneous fleet of clusters r can be a significant exercise.
Securing Your Kubernetes Environments via Network Policies
Today, one of the most significant benefits of Kubernetes is the ability to quickly deploy and connect applications, whether across namespaces in a cluster or across different cloud environments. By default, a pod/application running in a Kubernetes cluster has the freedom to communicate with anything inside and outside the cluster with no security rules applied.