Kubernetes Namespace Provisioning
Kubernetes Namespace Provisioning
This Flow turns namespace provisioning into a self-service request. A developer fills in a form (namespace name, team, environment, resource tier, owner email), the request is validated against naming conventions and reserved names, and a message with Approve and Deny buttons goes to the platform Slack channel. On approval the Flow provisions everything a team needs: the namespace itself (labeled by team, environment, and tier, with Prometheus scrape annotations), a ResourceQuota matching the requested tier, a deployer service account with an admin role binding scoped to the namespace, and a network policy restricting ingress to in-namespace traffic. The requester gets the access details in Slack, denials reply in the approval thread, and provisioning failures are reported with the namespace and error attached.
After importing, connect the Flow to your systems: configure the Kubernetes app installation with your API server URL and a provisioning token, and create a SLACK_CHANNEL_ID secret with the channel to post approvals and notifications to. The naming rules, resource tiers, and provisioned resource bodies are plain JavaScript in the validation and Create Resource blocks, so they are easy to adapt to your conventions.
KubernetesCreate Resource
KubernetesCreate Resource
KubernetesCreate Resource
KubernetesCreate Resource
KubernetesCreate Resource