You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a [Platform Engineer], I want to create/update a Helm chart for creating Google Subnets via Config Connector, so that I can define network ranges in a consistent manner.
Table of content
[[TOC]]
Details
Depends on VPC creation or references an existing VPC.
Manages subnet parameters like region, IP range, secondary ranges, etc.
Acceptance criteria
Dependencies updated.
Comprehensive README.md with usage, including sample values.
Out-of-the-box example (e.g., creating a subnet in a specified region).
At least one placeholder for a Prometheus rule (if network-related metrics apply).
Semantic Versioning in place.
All quality gates pass.
Definition of Ready
Detailed summary and acceptance criteria.
Clear instructions on referencing an existing VPC or creating a new one.
Gating checks pass.
Definition of Production Ready
Chart published in an OCI/Helm repo.
Default values for typical production subnets.
Pluto or other testing to verify compatibility.
Breaking changes or critical notes documented.
Process Release of the Chart
Each MR references the Issue.
Pipeline tests pass (lint, template checks).
Chart version bumped, release notes updated, merged after approval.
The text was updated successfully, but these errors were encountered:
As a [Platform Engineer], I want to create/update a Helm chart for creating Google Subnets via Config Connector, so that I can define network ranges in a consistent manner.
Table of content
[[TOC]]
Details
Acceptance criteria
README.md
with usage, including sample values.Definition of Ready
Definition of Production Ready
Process Release of the Chart
The text was updated successfully, but these errors were encountered: