Use protobuf in gardener components #2836
Labels
area/cost
Cost related
area/performance
Performance (across all domains, such as control plane, networking, storage, etc.) related
kind/enhancement
Enhancement, improvement, extension
priority/3
Priority (lower number equals higher priority)
How to categorize this issue?
/area performance cost
/kind enhancement
/priority normal
What would you like to be added:
Currently all gardener components are configured to accept and send requests with content type
application/json
.We should switch to protobuf (
application/vnd.kubernetes.protobuf
) by default, where possible.As we heavily make use of CRDs in our Seed clusters it might not be possible to switch the seed client connection settings to protobuf at all, as CRDs don't support protobuf. But at least for the garden client connection it should be possible.
A fallback to json can be defined for
acceptContentTypes
withapplication/vnd.kubernetes.protobuf;application/json
.Why is this needed:
Using protobuf should be more efficient and might safe some data transfer costs.
The text was updated successfully, but these errors were encountered: