Add support for json output

[corneliusweig]

Add support for json output

[corneliusweig]

Given that kubectl can-i --list does not support json/yaml output this sounds like a reasonable request. I'm not entirely sure what the schema should be though. This seems ok-ish for rakkess for pods:

{
  "resource": "pods",
  "description": "maybe describe what this is",
  "rules": [
    {
      "name": "job-controller",
      "kind": "ServiceAccount",
      "sa-namespace": "kube-system",
      "verbs": {
         "get": true,
         "update": false,
      }
    },
   ]
}

Does that make sense? Or am I missing something?

---

Similarly for rakkess:

{
  "role": "self",
  "description": "maybe describe what this is",
  "rules": [
    {
      "resource": "pods",
      "verbs": {
         "get": true,
         "update": false,
      }
    },
   ]
}

[yuvalavra]

Thanks for the quick response!
My use case for this is to take the output from rakkess for $resource, specifically the service accounts, to then search for pods assigned those service accounts. Basically asking which pods in the cluster have permission to do something with$resource. So for my use case the schema you proposed is great.

Other use cases may benefit from a more detailed schema that includes the rolebindings and clusterrolebindinges that grant the searched privileges, so it could be nice to include them if rakkess already has that info.

{
  "resource": "pods",
  "description": "maybe describe what this is",
  "rules": [
    {
      "name": "job-controller",
      "kind": "ServiceAccount",
      "sa-namespace": "kube-system",
      "verbs": {
         "get": true,
         "update": false,
      },
      "rolebindings": [
         {<rolebinding object>}, # or perhaps just the rolebindings names?
      ],
      "clusterrolebindings": [
         {<clusterrolebinding object>}, # or perhaps just the clusterrolebindings names?
      ],
    },
   ]
}