From c1f1c0626dd621a002608592047847e7add47dd2 Mon Sep 17 00:00:00 2001 From: Dr Nic Williams Date: Mon, 28 Oct 2019 14:13:18 +1000 Subject: [PATCH] base64 --decode works across Linux and MacOS Signed-off-by: Dr Nic Williams --- .../tools/kubeadm/troubleshooting-kubeadm.md | 2 +- .../en/docs/tasks/administer-cluster/access-cluster-api.md | 2 +- .../fr/docs/setup/independent/troubleshooting-kubeadm.md | 6 +++--- .../ja/docs/setup/independent/troubleshooting-kubeadm.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md index 067b3ddad83bb..2f51d5efd7469 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md @@ -152,7 +152,7 @@ Unable to connect to the server: x509: certificate signed by unknown authority ( - Verify that the `$HOME/.kube/config` file contains a valid certificate, and regenerate a certificate if necessary. The certificates in a kubeconfig file - are base64 encoded. The `base64 -d` command can be used to decode the certificate + are base64 encoded. The `base64 --decode` command can be used to decode the certificate and `openssl x509 -text -noout` can be used for viewing the certificate information. - Unset the `KUBECONFIG` environment variable using: diff --git a/content/en/docs/tasks/administer-cluster/access-cluster-api.md b/content/en/docs/tasks/administer-cluster/access-cluster-api.md index a85f0b14a2247..38c87eb582af6 100644 --- a/content/en/docs/tasks/administer-cluster/access-cluster-api.md +++ b/content/en/docs/tasks/administer-cluster/access-cluster-api.md @@ -98,7 +98,7 @@ export CLUSTER_NAME="some_server_name" APISERVER=$(kubectl config view -o jsonpath="{.clusters[?(@.name==\"$CLUSTER_NAME\")].cluster.server}") # Gets the token value -TOKEN=$(kubectl get secrets -o jsonpath="{.items[?(@.metadata.annotations['kubernetes\.io/service-account\.name']=='default')].data.token}"|base64 -d) +TOKEN=$(kubectl get secrets -o jsonpath="{.items[?(@.metadata.annotations['kubernetes\.io/service-account\.name']=='default')].data.token}"|base64 --decode) # Explore the API with TOKEN curl -X GET $APISERVER/api --header "Authorization: Bearer $TOKEN" --insecure diff --git a/content/fr/docs/setup/independent/troubleshooting-kubeadm.md b/content/fr/docs/setup/independent/troubleshooting-kubeadm.md index ba00d254c7d74..8b65422b36d52 100644 --- a/content/fr/docs/setup/independent/troubleshooting-kubeadm.md +++ b/content/fr/docs/setup/independent/troubleshooting-kubeadm.md @@ -164,9 +164,9 @@ Unable to connect to the server: x509: certificate signed by unknown authority ( "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes") ``` -- Vérifiez que le fichier `$HOME/.kube/config` contient un certificat valide, et  -re-générer un certificat si nécessaire. Les certificats dans un fichier kubeconfig  -sont encodés en base64. La commande `base64 -d` peut être utilisée pour décoder le certificat  +- Vérifiez que le fichier `$HOME/.kube/config` contient un certificat valide, et +re-générer un certificat si nécessaire. Les certificats dans un fichier kubeconfig +sont encodés en base64. La commande `base64 --decode` peut être utilisée pour décoder le certificat et `openssl x509 -text -noout` peut être utilisé pour afficher les informations du certificat. - Une autre solution consiste à écraser le `kubeconfig` existant pour l'utilisateur" admin ": diff --git a/content/ja/docs/setup/independent/troubleshooting-kubeadm.md b/content/ja/docs/setup/independent/troubleshooting-kubeadm.md index d150d8181936c..a4de4d32d8c58 100644 --- a/content/ja/docs/setup/independent/troubleshooting-kubeadm.md +++ b/content/ja/docs/setup/independent/troubleshooting-kubeadm.md @@ -152,7 +152,7 @@ Unable to connect to the server: x509: certificate signed by unknown authority ( - Verify that the `$HOME/.kube/config` file contains a valid certificate, and regenerate a certificate if necessary. The certificates in a kubeconfig file - are base64 encoded. The `base64 -d` command can be used to decode the certificate + are base64 encoded. The `base64 --decode` command can be used to decode the certificate and `openssl x509 -text -noout` can be used for viewing the certificate information. - Unset the `KUBECONFIG` environment variable using: