Test output of installing rbac policies is too noisy

[gnufied]

Looks like after #69868 got merged, our test output has become too noisy and we are printing entire globs of RBAC policies.

Oct 30 14:34:41.307: INFO: patching original content of *v1.ServiceAccount:
{
  "kind": "ServiceAccount",
  "apiVersion": "v1",
  "metadata": {
    "name": "csi-driver-registrar",
    "namespace": "default",
    "creationTimestamp": null
  }
}
Oct 30 14:34:41.307: INFO: patching original content of *v1.ClusterRole:
{
  "kind": "ClusterRole",
  "apiVersion": "rbac.authorization.k8s.io/v1",
  "metadata": {
    "name": "driver-registrar-runner",
    "creationTimestamp": null
  },

I do not think, this is necessary.

/sig storage

cc @pohly

[pohly]

It was useful while we started with loading .yaml and patching it and it might be useful again for some other developer who starts to do the same. But I agree, for continuous usage in CI it's less useful.

How about we remove the"patching original content" message (because it mostly represents what's in the .yaml file, except when it uses deprecated aliases) and keep the "creating ..." message? Should that be:

• multiple lines (as right now)
• a single line with a JSON dump of the item
• just a single line with the name of the item?

I'd prefer to see the content, but would be fine with having that in a single line because while less readable, the information is at least there when needed.

[pohly]

/assign

[davidz627]

+1 we seem to be logging all the deployment yamls including statefulsets etc. It is hard to see whats going on in the tests at all and probably adds non-trivial execution time as well over the span of hundreds of tests

I would recommend not dumping the items at all in the standard case and only logging actions i.e. creating csi-gce-pd-controller and errors i.e. failed creating csi-gce-pd-controller: {json_dump_here}.

/cc @davidz627