text: Title: Add [Conformance:Variant] to some tests that change from deployment to deployment
  Body: **Problem Statement:**
  Providers that absorb the upstream tests would like to give their customers a standard mechanism to validate their clusters, post setup.  As of today **[Conformance]** works for most things, but there are a known set of tests that vary due to opinionated differences around networking, security, etc...   and providing a complete skip list can be cumbersome. 
  
  **Proposed Solution(s):** 
  - Annotate  tests that do not/may not/will not work on downstream deployments with a **[Feature:Variant]** label.  
  
  Thoughts? 
  
  /cc @kubernetes/sig-testing 
  