knative
/
caching
mirror of https://github.com/knative/caching.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
caching/vendor/knative.dev/pkg/apis/istio/v1alpha3
History
mattmoor-sockpuppet 55b45efbc4 Auto-update dependencies (#39) 
Produced via:
  `dep ensure -update github.com/knative/test-infra knative.dev/pkg`
/assign @mattmoor
 		2019-06-28 08:25:07 -07:00
..
README.md Migrate to knative.dev/pkg (#35) 2019-06-26 13:56:06 -07:00
destinationrule_types.go Migrate to knative.dev/pkg (#35) 2019-06-26 13:56:06 -07:00
doc.go Migrate to knative.dev/pkg (#35) 2019-06-26 13:56:06 -07:00
gateway_types.go Migrate to knative.dev/pkg (#35) 2019-06-26 13:56:06 -07:00
register.go Auto-update dependencies (#39) 2019-06-28 08:25:07 -07:00
virtualservice_types.go Auto-update dependencies (#39) 2019-06-28 08:25:07 -07:00
zz_generated.deepcopy.go Migrate to knative.dev/pkg (#35) 2019-06-26 13:56:06 -07:00

README.md

What are these files?

These are Go structs for Istio CRD. We translated them from proto files in https://github.com/istio/api/tree/master/networking/v1alpha3 .

Why do we hand-translate from proto? i.e Why can't we vendor these?

Istio needs to run on many platforms and as a reason they represent their objects internally as proto. On Kubernetes, their API take in JSON objects and convert to proto before processing them.

So they have nothing we can vendor, except for the Go files that are generated by the proto compiler, which is not compatible with K8s API code-generator at all.

We may be able to donate our translation so they can maintain it themselves. See https://github.com/istio/istio/issues/6084.