Is Ontag run needed ?

[sowmyav27]

Follow up with the functional teams

• [ ] To see if Ontag is needed
• [ ] if it's being run as part of the other checks

[slickwarren]

I looked into this, and found the following:

All of the python OnTag jobs use each of the following python tests. most or part of these, which are mostly broken. We need to come up with a plan on moving these to GO. Basically, there are 3 buckets:

• creating k8s resources through Steve (deployments, secrets, etc.) (team Framework)
• RBAC tests for ^ (Collie)
• adding provisioning tests in GO for parity with what was there in python (Hostbusters)
  • linking tests together in GO (i.e. provision a cluster, then run cert-rotation go test on it)

cert_rotation 
test_app aka v3_catalog -> Mapps
bunch of rbac tests, on their own and nested in all of these tests -> Collie
configmap -> framework
snapshots_local -- already covered in GO by Hostbusters
global_role -> Collie
grb -> Collie
RBAC -> Collie
HPA -> framework
ingress -> for PIT
network_policy -> for PIT
node_annotation -> framework
node_label -> framework
node_template aka rke1_templates. Need to follow up but I believe this is only available in v3 client and can be kept in python? -- TBD but likely framework
registry aka registry_secret creation  -> framework
secrets -> framework
service_discovery -> for PIT
volumes -> framework

websocket -> framework
workload -> framework

In some huddles, we determined that:

• PIT team will work on the 'network checks' section of python -> go (ie. ingress, service_discovery, etc)
• Import clusters are enabled in Corral and GO but not linked together yet
• the go_ontag job shows how to link go tests together in one run, while the recurring_runs job shows how to use glue code for provisioning. Use these two to create a job that runs GO tests that uses output of a provisioning job for use with other GO tests

[sowmyav27]

@slickwarren original OnTag failure tracking, which has some more info - https://github.com/rancher/qa-tasks/issues/821 (in the latest comment)

[slickwarren]

more context - not all tests listed are explicitly for ontag, but still need to be considered when converting the test from python -> go. The skipped tests here should be ignored if explicitly working on ontag in Go

[slickwarren]

all provisioning checks are being pulled out of ontag, and have separate tickets. I've also created separate tickets for other teams to track the deprecation of onTag. Removing this from the hostbusters board