SUMO-113170 Support different k8s api versions

[yuting-liu]

• Add support for different k8S api versions with multiple clients.
• Add unit tests.

[yuting-liu]

ci/build.sh successfully run on my machine locally but seems failed here. Will investigate it.

[maimaisie]

If you haven't, let's make sure to run the plugin with the beta1 api version and check if events are getting ingested to Sumo. I feel like because we are stubbing all client methods in the unit tests, we are not really testing the logic "given a different API version it will call different endpoint". Technically, if you set beta1 version in the config param in a unit test and call mock_get_events with the v1 file, it would still succeed

[samjsong]

LGTM with one minor comment. +1 to Maisie's comment that we should try testing to see how it works when deployed

[yuting-liu]

Already tested the plugin, with api version apps/v1 and resourceName deployments.
We do get both log lines that there are two clients created, one for v1, the other for apps/v1:

create client with URL: https://XX.XX.X.X:XXX/api and apiVersion: v1
create client with URL: https://XX.XX.X.X:XXX/apis and apiVersion: apps/v1

Here is what we got from watch:

{  
   "type":"ADDED",
   "object":{  
      "kind":"Deployment",
      "apiVersion":"apps/v1",
      "metadata":{  
         "name":"fluentd-events",
         "namespace":"sumologic",
         "selfLink":"/apis/apps/v1/namespaces/sumologic/deployments/fluentd-events",
         "uid":"64720983-a984-11e9-80e5-025000000001",
         "resourceVersion":"2771498",
         "generation":1,
         "creationTimestamp":"2019-07-18T17:49:29Z",
         "labels":{  
            "k8s-app":"fluentd-sumologic"
         },
         ...
}

So this do watch the correct resource with correct api version.

[maimaisie]

is this log ingested in Sumo?

[yuting-liu]

@maimaisie Yea, the log is ingested in Sumo.