@IronMan

I definitely agree with your perspective, but I believe there are some challenges we need to consider.

First, Pega is not widely used as a standalone enterprise application. In most organizations, it operates in conjunction with multiple other applications. This interdependency means that a Pega Admin's role can sometimes feel limited, as managing just Pega alone often doesn’t fill a full 8-hour workday. Furthermore, with Pega now offered as a SaaS, cloud teams handle upgrades and maintenance, further reducing the scope of traditional Pega Admin responsibilities.

In light of this, I feel the roles of Pega Admin and Pega Production Support could be combined into a single role with appropriate certifications and career paths. This would not only broaden the responsibilities of the role but also make it more sustainable for organizations.

Regarding Kubernetes and cloud infrastructure, I agree that Pega needs to provide more transparency and detailed insights into how its cloud environment is set up. While there are some courses available from Pega, they don’t seem to be as effective as they could be. Additionally, when issues arise on the Pega Cloud side, there is often confusion about responsibility when opening SRs. This is compounded by the fact that the Pega Cloud team has more access to cloud infrastructure than other support teams or developers, creating a knowledge and access gap.

From a developer's perspective, it’s clear that Pega SaaS is still in its early stages and evolving. Coupled with the introduction of new features like Constellation in Pega Infinity 23 and 24, it’s a challenge for both developers and admins to gain mastery in these areas quickly. The ecosystem is still maturing, and I completely understand and respect the frustration that comes with navigating these growing pains.

Thank you for highlighting these important points. It’s a discussion worth continuing to ensure the Pega ecosystem evolves in the right direction.