From ea2b7b6700859434f991120e4a4a1d2d3e7b966c Mon Sep 17 00:00:00 2001 From: Avi Weit Date: Thu, 7 Nov 2019 11:54:42 +0200 Subject: [PATCH] Fix typo --- docs/rest-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rest-api.md b/docs/rest-api.md index c88a5698de7c..b8661fe13a9c 100644 --- a/docs/rest-api.md +++ b/docs/rest-api.md @@ -2,7 +2,7 @@ Argo is implemented as a kubernetes controller and Workflow [Custom Resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). Argo itself does not run an API server, and with all CRDs, it extends the Kubernetes API server by -introducing a new API Group/Version (argorproj.io/v1alpha1) and Kind (Workflow). When CRDs are +introducing a new API Group/Version (argoproj.io/v1alpha1) and Kind (Workflow). When CRDs are registered in a cluster, access to those resources are made available by exposing new endpoints in the kubernetes API server. For example, to list workflows in the default namespace, a client would make an HTTP GET request to: `https:///apis/argoproj.io/v1alpha1/namespaces/default/workflows`