Inconsistent resource naming

[rfranzke]

What would you like to be added:
In a shoot, the rolebindings have inconsistent names:

$ ks get rolebinding
NAME                                                                AGE
...
garden.sapcloud.io:psp:calico                                       24h
garden.sapcloud.io:psp:calico-kube-controllers                      24h
garden.sapcloud.io:psp:calico-typha                                 24h
...
gardener.cloud:psp:typha-cpa                                        24h
gardener.cloud:psp:typha-cpva                                       24h
...
typha-cpha                                                          24h

It probably makes sense to also check the other resources.

Why is this needed:
Consistency

[ialidzhikov]

The garden.sapcloud.io: prefixed ones are already switched to gardener.cloud with #7.

[rfranzke]

Hm, probably the old names are not cleaned up for existing shoots? See above, this was a new cluster created 24h ago - why do the rolebindings have the same creation timestamps?

[ialidzhikov]

Probably your extension version is v1.3.0? The referenced change above is still not released.

[rfranzke]

Ah okay, understood. Thank you! So, the only "open inconsistency" is

$ ks get rolebinding
NAME                                                                AGE
...
gardener.cloud:psp:typha-cpa                                        24h
gardener.cloud:psp:typha-cpva                                       24h
...
typha-cpha     

?

[ialidzhikov]

This typha-cpha RoleBinding is not for PSP, but generally I agree that we could prefix it with gardener.cloud for consistency. There might be also others.

[rfranzke]

Yes, probably it should even be prefixed with networking.gardener.cloud:calico:... or something similar.