Skip to content

Commit 4f58902

Browse files
committed
address feedback - round 1
1 parent f9d7db7 commit 4f58902

File tree

2 files changed

+7
-18
lines changed

2 files changed

+7
-18
lines changed

sigs.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3637,8 +3637,8 @@ workinggroups:
36373637
slack: wg-api-expression
36383638
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-api-expression
36393639
liaison:
3640-
github: BenTheElder
3641-
name: Benjamin Elder
3640+
github: pohly
3641+
name: Patrick Ohly
36423642
- dir: wg-batch
36433643
name: Batch
36443644
mission_statement: >

wg-api-expression/charter.md

Lines changed: 5 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -39,13 +39,15 @@ The working group will deliver:
3939
- **Kube API Linter (KAL)**: Automated API convention checker integrated into the review process
4040
- **Integration strategy**: Cohesive approach for integrating validation-gen, kubebuilder, KAL, and other tools
4141
- **KEPs**: Series of enhancement proposals introducing and evolving the framework
42-
- **CRD equivalence strategy**: Plan to bridge the gap between native types and CRDs
43-
- **Documentation generation strategy**: Automated documentation from declarative API expressions
42+
- **Native Type and CRD Validation Parity**: Bridge the gap between how validation is implemented for native Kubernetes types and CRDs to unify the developer experience and improve APIs. This strategy includes:
43+
- Establishing a declarative source of truth (e.g., Go struct tags) for validation rules that can generate the validation methods needed for native types and the OpenAPI/CEL rules used by CRDs.
44+
- Enable easier inheritance of validation logic when a CRD embeds a native type. For example, a CRD that includes a `corev1.PodSpec` should allow reuse of `PodSpec`'s validation.
45+
- **Automated API Reference Documentation**: A strategy and tooling to automatically generate documentation for validation rules directly from the declarative tags in the Go API types. The goal is to enhance Kubernetes API reference docs by ensuring they are synchronized with the validation logic enforced by the API server.
4446
- **Migration guides**: Documentation for SIGs to adopt the framework and migrate existing APIs
4547

4648
## Stakeholders
4749

48-
- **SIG API Machinery**: Owner of API server, gengo, kube-openapi, and validation-gen tool
50+
- **SIG API Machinery**: Owner of API server, gengo, kube-openapi, kube-api-linter, and validation-gen tool
4951
- **SIG Architecture**: Owner of Kubernetes API conventions and architectural decisions
5052
- **SIG CLI**: Consumer of more expressive APIs, providing feedback on kubectl interaction and user experience
5153

@@ -54,19 +56,6 @@ The working group will deliver:
5456
This sig adheres to the Roles and Organization Management outlined in [sig-governance]
5557
and opts-in to updates and modifications to [sig-governance].
5658

57-
### Meeting Mechanics
58-
59-
- **Frequency**: Bi-weekly (every 2 weeks)
60-
- **Duration**: 60 minutes
61-
- **Communication**:
62-
- Slack: #wg-api-expression
63-
- Mailing List: [email protected]
64-
65-
### Chairs
66-
67-
- Aaron Prindle (@aaron-prindle)
68-
- Joel Speed (@JoelSpeed)
69-
7059
## Exit Criteria
7160

7261
The working group will have fulfilled its charter and can be disbanded when:

0 commit comments

Comments
 (0)