From 7ea1c9b760ff340bc784ff3314053ed58ba9f1ce Mon Sep 17 00:00:00 2001 From: Pooneh Mortazavi Date: Fri, 13 Dec 2019 16:50:22 -0800 Subject: [PATCH] Fix documentation for multi-cluster allocation --- .../en/docs/Advanced/multi-cluster-allocation.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/site/content/en/docs/Advanced/multi-cluster-allocation.md b/site/content/en/docs/Advanced/multi-cluster-allocation.md index 3cd799b484..7aae09e2ef 100644 --- a/site/content/en/docs/Advanced/multi-cluster-allocation.md +++ b/site/content/en/docs/Advanced/multi-cluster-allocation.md @@ -47,7 +47,7 @@ To accept allocation requests from other clusters, agones-allocator for cluster Follow the steps to configure the [agones allocator REST API service]({{< relref "allocator-service.md">}}). The client certificate pair in the mentioned document is stored as a K8s secret. Here are the secrets to set: -1. Client certificate to talk to other clusters: +1.Client certificate to talk to other clusters: ```bash cat < - client.key: + tls.crt: + tls.key: ca.crt: EOF ``` @@ -67,7 +68,7 @@ The certificates are base 64 string of the certificate file e.g. `cat ${CERT_FIL `ca.crt` is the server TLS public certificate if it is self-signed. For simplicity, it is recommended to use one client secret per cluster and make `ca.crt` bundle of server certificates. -2. Add client CA to the list of authorized client certificates by agones-allocator in the targeted cluster. +2.Add client CA to the list of authorized client certificates by agones-allocator in the targeted cluster. ```bash cat < client2.crt: … @@ -96,7 +98,7 @@ FLEET_NAME= curl https://${EXTERNAL_IP}:443/v1alpha1/gameserverallocation \ --header "Content-Type: application/json" \ - -d '{"namespace": "'${NAMESPACE}'", "multiClusterSetting": {"enabled": true}, "requiredGameServerSelector": {"matchLabels": {"stable.agones.dev/fleet": "'${FLEET_NAME}'"}}}' \ + -d '{"namespace": "'${NAMESPACE}'", "multiClusterSetting": {"enabled": true}, "requiredGameServerSelector": {"matchLabels": {"agones.dev/fleet": "'${FLEET_NAME}'"}}}' \ --key ${KEY_FILE} \ --cert ${CERT_FILE} \ --cacert ${TLS_CERT_FILE} -v