From 5d13ea97a736fd3a51cdf1a87d2eba00b5ccfaec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicolas=20Mass=C3=A9?= Date: Fri, 7 Jun 2019 17:44:15 +0200 Subject: [PATCH] fix typo --- content/blog/use-qlkube-to-query-the-kubernetes-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/use-qlkube-to-query-the-kubernetes-api.md b/content/blog/use-qlkube-to-query-the-kubernetes-api.md index dee9f52..f34a8d7 100644 --- a/content/blog/use-qlkube-to-query-the-kubernetes-api.md +++ b/content/blog/use-qlkube-to-query-the-kubernetes-api.md @@ -325,7 +325,7 @@ EOF ## Advanced use-cases -One use case in which GraphQL is very interesting is the ability to request in the same query an object and it's linked objects. For instance, it would be nice from a hostname to query the route that matches this hostname, along with the service backing this routes and the pods behind the service. +One use case in which GraphQL is very interesting is the ability to request in the same query an object and it's linked objects. For instance, it would be nice from a hostname to query the route that matches this hostname, along with the service backing this route and the pods behind the service. Unfortunately, this is not yet possible with GLKube. Since it auto-generates its GraphQL schema from the OpenAPI Specifications of the Kubernetes APIs and those APIs are loosely coupled, some code would be required to link the relevant object between them.