Tracking issue - Identify API-Machinery e2e tests to be promoted to conformance and evaluate gaps in coverage about k8s-conformance

[AishSundar]

/cc @mayankg @akurylec @joseluis

[AishSundar]

Tracking sheet - https://docs.google.com/spreadsheets/d/1p_xzVmK4uKC8oh1UBgXVcqGHC1YaYrppn55KrcgUyMk/edit#gid=0

[AishSundar]

Working with Api-machinery SIG offline (@fedebongio, @jennybuckley), they have identified the following existing e2e tests to be promoted to conformance suite in v1.12. (Tracker sheet).

• [sig-api-machinery] Aggregator Should be able to support the 1.7 Sample API Server using the current Aggregator (already in progress in 1.11)
• [sig-api-machinery] Garbage collector should delete jobs and pods created by cronjob
• [sig-api-machinery] Garbage collector should orphan pods created by rc if deleteOptions.OrphanDependents is nil
• [sig-api-machinery] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted.
• [sig-api-machinery] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted.
• [sig-api-machinery] Servers with support for API chunking should return chunks of results for list calls

As next steps,

• Globant vendors will be running these tests to ensure they pass flakiness criteria, do not skip providers etc
• Globant vendors will be creating PRs to promote these cases to Conformance and get initial review from Api-machinery SIG, before looping in Sig-Architecture for review.

/cc @mgdevstack

[AishSundar]

@fedebongio and @WilliamDenniss Need some clarity / guidance on promoting / rewriting the following e2e tests

• kubernetes/kubernetes#65427
• kubernetes/kubernetes#65428

[hh]

/close
I think this issue is stale.