Kubectl Non-Interactive Session, created 3 events. Not clear that it's Kubectl related

[benarent]

Description

What happened:
While testing our Kubernetes integration, we create three events for a command.

My thoughts are..

1. If proto is kube, don't define as a session.start event.
2. Why doesn't our integration capture the ls?
3. Why do have a resize event?
4. We know the addr.local = 1126XXX.gr7.us-west-2.eks.amazonaws.com:443 we should use that vs 'node' in the UI

➜  ~ kubectl exec -ti  --namespace=kube-system kube-proxy-7w4z4 ls
{
  "addr.local": "1126XXX.gr7.us-west-2.eks.amazonaws.com:443",
  "addr.remote": "73.202.138.51:43848",
  "code": "T2000I",
  "ei": 0,
  "event": "session.start",
  "login": "benarent",
  "namespace": "default",
  "proto": "kube",
  "server_id": "fd456f7c-2f9d-4f8f-b51f-fd3b70351c0d",
  "sid": "73af5f8c-acde-401e-a382-a0713443dc7e",
  "size": "100:100",
  "time": "2020-06-29T22:59:37.195Z",
  "uid": "00cb47f7-f0ff-484b-a529-3e40ff1f27d9",
  "user": "benarent"
}
{
  "code": "T2002I",
  "ei": 1,
  "event": "resize",
  "login": "benarent",
  "namespace": "default",
  "proto": "kube",
  "sid": "73af5f8c-acde-401e-a382-a0713443dc7e",
  "size": "181:54",
  "time": "2020-06-29T22:59:37.399Z",
  "uid": "fc69a9bd-c93e-4c5b-9422-6cf4b5c509a3",
  "user": "benarent"
}
{
  "code": "T2004I",
  "ei": 3,
  "event": "session.end",
  "namespace": "default",
  "proto": "kube",
  "sid": "73af5f8c-acde-401e-a382-a0713443dc7e",
  "time": "2020-06-29T22:59:37.455Z",
  "uid": "8a7b679d-4299-4f99-9fe1-0d4d3a355599",
  "user": "benarent"
}

[benarent]

Duplicate of #4055

[awly]

The UI parts are mostly fixed.
We can still capture the provided command, added that to #3528