Locally representing a remote application programming interface (API) endpoint within an application platform

1. A computer-implemented method comprising:

receiving, by an application platform operating within a public cloud, information regarding a forwarding proxy associated with a private network and information regarding a remote application programming interface (API) endpoint within the private network;

creating, by a controller of the application platform, a mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy by causing the forwarding client to instantiate a port corresponding to a forwarding route for the remote API endpoint based on the information regarding the forwarding proxy and the remote API endpoint; and

locally representing the remote API endpoint within the application platform in a form of an instance of a service abstraction provided by the application platform by:

configuring an instance of an endpoint abstraction provided by the application platform that maps a name and port of the remote API endpoint to an address and the port of the forwarding client; and

configuring endpoint attributes of the instance of the service abstraction with a protocol of the remote API endpoint and a reference to the instance of the endpoint abstraction.

2. The computer-implemented method of claim 1 , wherein the application platform comprises a container cluster, the service abstraction comprises a container orchestrator service resource, and the endpoint abstraction comprises a container orchestrator endpoints resource.

3. The computer-implemented method of claim 2 , further comprising when the information regarding the remote API endpoint includes a domain name in a domain of the private network, creating, by the controller, a corresponding Domain Name System (DNS) entry in a private DNS zone of an upstream nameserver associated with the container cluster.

4. The computer-implemented method of claim 3 , wherein when the instance of the service abstraction has a cluster Internet Protocol (IP) address, then the corresponding DNS entry associates the cluster IP address with a name in the corresponding DNS entry.

5. The computer-implemented method of claim 3 , wherein when the instance of the service abstraction comprises a headless service, then the corresponding DNS entry associates the address and the port of the forwarding client with a name in the corresponding DNS entry.

6. The computer-implemented method of claim 1 , wherein the information regarding the forwarding proxy comprises a universal unique identifier (UUID).

7. The computer-implemented method of claim 1 , wherein the information regarding the remote API endpoint comprises a name of the remote API endpoint, an address of the remote API endpoint in an addressing scheme of the private network, a port of the remote API endpoint and a protocol used by the remote API endpoint.

8. The computer-implemented method of claim 1 , wherein said mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy facilitates communication with the remote API endpoint by a container in the application platform by allowing the container to direct network traffic intended for the remote API endpoint to the port on the forwarding client.

9. A non-transitory machine readable medium storing instructions executable by a processing resource of an application platform operating within a public cloud, the non-transitory machine readable medium comprising instructions to:

receive information regarding a forwarding proxy associated with a private network and information regarding a remote application programming interface (API) endpoint within the private network;

create, by a controller of the application platform, a mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy by causing the forwarding client to instantiate a port corresponding to a forwarding route for the remote API endpoint based on the information regarding the forwarding proxy and the remote API endpoint;

locally represent the remote API endpoint within the application platform in a form of an instance of a service abstraction provided by the application platform by:

configuring an instance of an endpoint abstraction provided by the application platform that maps a name and port of the remote API endpoint to an address and the port of the forwarding client; and

configuring endpoint attributes of the instance of the service abstraction with a protocol of the remote API endpoint and a reference to the instance of the endpoint abstraction.

10. The non-transitory machine readable medium of claim 9 , wherein the application platform comprises a container cluster, the service abstraction comprises a container orchestrator service resource, and the endpoint abstraction comprises a container orchestrator endpoints resource.

11. The non-transitory machine readable medium of claim 10 , further comprising instructions to when the information regarding the remote API endpoint includes a domain name in a domain of the private network, create, by the controller, a corresponding Domain Name System (DNS) entry in a private DNS zone of an upstream nameserver associated with the container cluster.

12. The non-transitory machine readable medium of claim 11 , when the instance of the service abstraction has a cluster Internet Protocol (IP) address, then the corresponding DNS entry associates the cluster IP address with a name in the corresponding DNS entry.

13. The non-transitory machine readable medium of claim 11 , wherein when the instance of the service abstraction comprises a headless service, then the corresponding DNS entry associates the address and the port of the forwarding client with a name in the corresponding DNS entry.

14. The non-transitory machine readable medium of claim 9 , wherein the information regarding the forwarding proxy comprises a universal unique identifier (UUID).

15. The non-transitory machine readable medium of claim 9 , wherein the information regarding the remote API endpoint comprises a name of the remote API endpoint, an address of the remote API endpoint in an addressing scheme of the private network, a port of the remote API endpoint and a protocol used by the remote API endpoint.

16. The non-transitory machine readable medium of claim 9 , wherein said mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy facilitates communication with the remote API endpoint by a container in the application platform by allowing the container to direct network traffic intended for the remote API endpoint to the port on the forwarding client.

17. A system comprising:

a processing resource; and

a non-transitory computer-readable medium, coupled to the processing resource, having stored therein instructions that when executed by the processing resource cause the processing resource to:

receive, by an application platform, information regarding a forwarding proxy associated with a private network and information regarding a remote application programming interface (API) endpoint within the private network;

create, by a controller of the application platform, a mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy by causing the forwarding client to instantiate a port corresponding to a forwarding route for the remote API endpoint based on the information regarding the forwarding proxy and the remote API endpoint;

locally represent the remote API endpoint within the application platform in a form of an instance of a service abstraction provided by the application platform by:

configuring an instance of an endpoint abstraction provided by the application platform that maps a name and port of the remote API endpoint to an address and the port of the forwarding client; and

configuring endpoint attributes of the instance of the service abstraction with a protocol of the remote API endpoint and a reference to the instance of the endpoint abstraction.

18. The system of claim 17 , wherein the application platform comprises a container cluster, the service abstraction comprises a container orchestrator service resource, and the endpoint abstraction comprises a container orchestrator endpoints resource.

19. The system claim 17 , wherein the instructions further cause the processing resource to when the information regarding the remote API endpoint includes a domain name in a domain of the private network, create, by the controller, a corresponding Domain Name System (DNS) entry in a private DNS zone of an upstream nameserver associated with the container cluster.

20. The system of claim 17 , wherein said mapping between a resource model of the application platform to a tunnel established between a forwarding client of the application platform and the forwarding proxy facilitates communication with the remote API endpoint by a container in the application platform by allowing the container to direct network traffic intended for the remote API endpoint to the port on the forwarding client.