Support Pods Iteration 2: FlexiPod leads

As part of Support Pods Iteration 2, I'm looking for FlexiPod leads who will be accountable for the purpose, recruitment and functioning of their FlexiPod.

FlexiPod leads are also expected to collaborate with other FlexiPod leads to shape, define and document their own role and responsibilities.

FlexiPod leads can choose to be accountable for one of the existing Support Pods:

• Authentication
• CI/CD
• GitLab Features
• Instance Management
• Managing Group / Project
• Secure

Alternatively, FlexiPod leads can choose to start up a new FlexiPod in any topic area of their choosing.

If two or more people have a strong interest in the same area, I strongly suggest coming together to work together in the same FlexiPod as we need to experiment with:

• Collaboration between members of a Support Pod, especially across timezones with little overlap.
• Having a deputy Support Pod lead role to prevent single points of failure.

You can still greatly contribute to the Iteration 2 Pilot even if you are not a named FlexiPod lead!

Sign-up sheet

FlexiPod Name	Description	Lead
Secure	Secure stage features	@greg & @katrinleinweber-gtlb
Authentication	Any tickets that are related to Omniauth, SAML, SCIM, LDAP, and authentication issues	@asmaa.hassan, @arihantar, @gerardo
Geo	Any tickets covering Geo	@rvzon & @anton
14.x Upgrade Readiness	To enable readiness around potential issues (and workarounds) when upgrading versions in 14.x.	@alvin
Getting comfortable with K8s	Focus on dealing with k8s related tickets to gain more experience. 3 main usage of K8s within GitLab. Helm chart GitLab installation, K8s Runner (helm or k8s executor), and CD (managed apps / k8s agent). At this point, this pod will look into all. We may divide this into smaller pods.	@awinata + regional co-lead?