From 67e4f54aaa5de8cb767acec9d9b852638201c64f Mon Sep 17 00:00:00 2001 From: Dan Kohn Date: Tue, 27 Jun 2017 10:44:35 -0400 Subject: [PATCH] Replace remaining kargo usages to kubespray --- docs/getting-started-guides/kubespray.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/getting-started-guides/kubespray.md b/docs/getting-started-guides/kubespray.md index 404176aa29..17c1e446bc 100644 --- a/docs/getting-started-guides/kubespray.md +++ b/docs/getting-started-guides/kubespray.md @@ -32,7 +32,7 @@ to [kubeadm](../kubeadm) and [kops](../kops). * You must have cloud instances or baremetal nodes running for your future Kubernetes cluster. A way to achieve that is to use the - [kargo-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md). + [kubespray-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md). * Or provision baremetal hosts with a tool-of-your-choice or launch cloud instances, then create an inventory file for Ansible with this [tool](https://github.com/kubernetes-incubator/kubespray/blob/master/contrib/inventory_builder/inventory.py). @@ -65,7 +65,7 @@ to [kubeadm](../kubeadm) and [kops](../kops). #### Checklist * Apply deployment with - [kargo-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md) + [kubespray-cli tool](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md) or ``ansible-playbook`` [manual commands](https://github.com/kubernetes-incubator/kubespray/blob/master/docs/getting-started.md#starting-custom-deployment). @@ -95,6 +95,5 @@ Note, that it is highly unrecommended to delete production clusters with the res ## Feedback -* Slack Channel: [#kargo](https://kubernetes.slack.com/messages/kargo/) +* Slack Channel: [#kubespray](https://kubernetes.slack.com/messages/kubespray/) * [GitHub Issues](https://github.com/kubernetes-incubator/kubespray/issues) -