Now we are all set; if you've completed the deployment of utcdate-service and isodate-service, a fully working system should be installed on Kubernetes. The way it works is very simple: When you get the URL of the aggregator in the /dates/{timestamp} path, replacing timestamp with a valid UNIX timestamp, the service will contact utcdate-service and isodate-service and get the timestamp converted into the UTC and ISO formats. In my case, the load balancer provided by Google Cloud Platform will lead to the URL: http://104.155.35.237/dates/1111111111.
It will have the following response:
{ utcDate: "2005-03-18T01:58:31", isoDate: "2005-03-18T01:58:31.000Z"}
You can play around with it for a bit, but it is nothing fancy: just ...
