Extending enterprise trusted policy framework to cloud native applications

1. At least one non-transitory computer readable medium comprising instructions stored thereon, the instructions being effective to cause at least one processor to:

receive, by a service mesh orchestrator for a service mesh from an enterprise network controller, a first communication, wherein the first communication informs the service mesh orchestrator of traffic segmentation policies to be applied to traffic originating at an enterprise network and of layer 7 extension headers which correspond to the traffic segmentation policies; and

apply, by the service mesh orchestrator, the traffic segmentation polices on the service mesh; and

handle network traffic, from the enterprise network at the service mesh, in accordance with the traffic segmentation polices.

2. The at least one non-transitory computer readable medium of claim 1 , further comprising instructions effective to cause the at least one processor to:

send, by the enterprise network controller, a second communication to a data plane translation service, wherein the second communication instructs the data plane translation service to translate layer 2 or 3 fields for network traffic destined for the service mesh into the layer 7 extension headers prior to forwarding the network traffic to the service mesh.

3. The at least one non-transitory computer readable medium of claim 2 , wherein the layer 2 or 3 fields include an SGT field and a VNI field, which are translated into extension headers for HTTP(S) network traffic.

4. The at least one non-transitory computer readable medium of claim 1 , further comprising instructions effective to cause the at least one processor to:

send, by the enterprise network controller, a second communication to an enterprise edge network device of the enterprise network, wherein the second communication instructs the enterprise edge network device to insert layer 7 extension headers for use in traffic segmentation into network traffic destined for the service mesh prior to encapsulating the network traffic into a VXLAN tunnel between the enterprise edge network device and an enterprise border network device of the enterprise network.

5. The at least one non-transitory computer readable medium of claim 4 , wherein the second communication further instructs the enterprise edge network device to send metadata describing the network traffic, and wherein the first communication further instructs the service mesh of granular network policies to be applied to the network traffic based on the metadata.

6. The at least one non-transitory computer readable medium of claim 2 , wherein the second communication further instructs the data plane translation service to:

receive layer 7 network traffic from the service mesh;

detect the layer 7 extension headers;

encapsulate the network traffic into a VXLAN tunnel between an enterprise border network device of the enterprise network and the data plane translation service; and

create the layer 2 or 3 fields based on the detected layer 7 extension headers.

7. A method comprising:

receiving, by a service mesh orchestrator for a service mesh from an enterprise network controller, a first communication to, wherein the first communication informs the service mesh orchestrator of traffic segmentation policies to be applied to traffic originating at an enterprise network and of layer 7 extension headers which correspond to the traffic segmentation policies;

applying, by the service mesh orchestrator, the traffic segmentation polices on the service mesh; and

handling network traffic, from the enterprise network at the service mesh, in accordance with the traffic segmentation polices.

8. The method of claim 7 , further comprising:

sending, by the enterprise network controller, a second communication to a data plane translation service, wherein the second communication instructs the data plane translation service to translate layer 2 or 3 fields for network traffic destined for the service mesh into the layer 7 extension headers prior to forwarding the network traffic to the service mesh.

9. The method of claim 8 , wherein the layer 2 or 3 fields include an SGT field and a VNI field, which are translated into extension headers for HTTP(S) network traffic.

10. The method of claim 7 , further comprising:

sending, by the enterprise network controller, a second communication to an enterprise edge network device of the enterprise network, wherein the second communication instructs the enterprise edge network device to insert layer 7 extension headers for use in traffic segmentation into network traffic destined for the service mesh prior to encapsulating the network traffic into a VXLAN tunnel between the enterprise edge network device and an enterprise border network device of the enterprise network.

11. The method of claim 10 , wherein the second communication further instructs the enterprise edge network device to send metadata describing the network traffic, and wherein the first communication further instructs the service mesh of granular network policies to be applied to the network traffic based on the metadata.

12. The method of claim 8 , wherein the second communication further instructs the data plane translation service to:

receive layer 7 network traffic from the service mesh;

detect the layer 7 extension headers;

encapsulate the network traffic into a VXLAN tunnel between an enterprise border network device of the enterprise network and the data plane translation service; and

create the layer 2 or 3 fields based on the detected layer 7 extension headers.

13. A system comprising:

a service mesh orchestrator of a service mesh configured to receive, from an enterprise network controller of an enterprise network, a first communication informing a service mesh orchestrator of traffic segmentation policies to be applied to traffic originating at an enterprise network and of layer 7 extension headers which correspond to the traffic segmentation policies;

apply the traffic segmentation polices on the service mesh; and

handle network traffic, from the enterprise network at the service mesh, in accordance with the traffic segmentation polices.

14. The system of claim 13 , wherein the enterprise network controller is further configured to send a second communication to a data plane translation service, wherein the second communication instructs the data plane translation service to translate layer 2 or 3 fields for network traffic destined for the service mesh into the layer 7 extension headers prior to forwarding the network traffic to the service mesh.

15. The system of claim 14 , wherein the layer 2 or 3 fields include an SGT field and a VNI field, which are translated into extensions headers for HTTP(S) network traffic.

16. The system of claim 13 , wherein the enterprise network controller is further configured to send a second communication to an enterprise edge network device of the enterprise network, wherein the second communication instructs the enterprise edge network device to insert layer 7 extension headers for use in traffic segmentation into network traffic destined for the service mesh prior to encapsulating the network traffic into a VXLAN tunnel between the enterprise edge network device and an enterprise border network device of the enterprise network.

17. The system of claim 16 , wherein the second communication further instructs the enterprise edge network device to send metadata describing the network traffic, and wherein the first communication further instructs the service mesh of granular network policies to be applied to the network traffic based on the metadata.

18. The system of claim 14 , wherein the second communication further instructs the data plane translation service to:

receive layer 7 network traffic from the service mesh;

detect the layer 7 extension headers;

encapsulate the network traffic into a VXLAN tunnel between an enterprise border network device of the enterprise network and the data plane translation service; and

create the layer 2 or 3 fields based on the detected layer 7 extension headers.