Open qicz opened 5 days ago
does GatewayAPI support protobuf?
does GatewayAPI support protobuf?
raised PR https://github.com/kubernetes-sigs/gateway-api/issues/3346
I didn't found too much docs for this, how can we achieve this?
https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources @zirain
I'm asking how to make our api support it? does EG need any code change?
https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources @zirain
I'm asking how to make our api support it? does EG need any code change?
add protobuf
tag in API struct
https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources @zirain
I'm asking how to make our api support it? does EG need any code change?
add
protobuf
tag in API struct
can you share an existing project that do such things as demo.
https://kubernetes.io/docs/reference/using-api/api-concepts/#alternate-representations-of-resources @zirain
I'm asking how to make our api support it? does EG need any code change?
add
protobuf
tag in API structcan you share an existing project that do such things as demo.
client-go and go-controller-panel have more places using protobuf
go-control-plane generated from proto to go struct, so I thinks that's not valid example?
for client-go, I cannot find the tag protobuf
you said.
In order for the API server to be able to decode protobuf-encoded resources, the protobuf definitions need to be compiled into the API server.
In Kubernetes, sending the API server protobuf encoded resources only works for core resources, and not for CRDs.
As written here:
Not all API resource types support Protobuf; specifically, Protobuf isn't available for resources that are defined as CustomResourceDefinitions or are served via the aggregation layer.
In order for the API server to be able to decode protobuf-encoded resources, the protobuf definitions need to be compiled into the API server.
In Kubernetes, sending the API server protobuf encoded resources only works for core resources, and not for CRDs.
As written here:
Not all API resource types support Protobuf; specifically, Protobuf isn't available for resources that are defined as CustomResourceDefinitions or are served via the aggregation layer.
yep, just core types support protobuf
. https://github.com/kubernetes/kubernetes/issues/55541
we can support core types by protobuf
and crd by json
with two client instances. Any other suggestions?
cc @zirain
we can support core types by protobuf and crd by json with two client instances
sgtm
we can support core types by
protobuf
and crd byjson
with two client instances. Any other suggestions?cc @zirain
Controller-runtime
based clients already uses protobuf for types that support it.
See https://github.com/kubernetes-sigs/controller-runtime/pull/1149
Description:
[optional Relevant Links:]