implementing our way of converting ingress objects into envoy resources #8
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
add some functions to convert ingress into envoy resources.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
At present, we use contour's code to transfer ingress objects into envoy resources, such as secret and so on. The license of contour is apache 2.0, so it would cause trouble if we want to contribute the envoy ingress controller to the kubeedge community. So it's a necessary that we convert it our way. The implementation can be written as a sdk.