After merging, Cedric Ollivier to author the tables for SIGs that have tests already specified
RA2 team to specify, for each feature, whether it's mandatory or not - some items may require fleshing out
idea is for RC2 to sync automatically with content of table once it's completed
Issue 2341: as RC is run against a specific K8S API, request is to be prescriptive and mandate/specify an exact API and version for all RA2 K8S components
Criteria to decide whether an API version is acceptable: follow upstream K8S ref implementation? Propose to use whatever upstream uses
Defining a min reference k8s release does not implicitly mandate an API version - must decide among the non-deprecated versions within a k8s release
Minimum set of k8s objects for RA2 compliance must be defined before specifying the API for each - get from upstream