Merge pull request #1259 from mtulio/patch-1

docs: fix broken references on getting_started.md

Author: k8s-ci-robot

docs/getting_started.md

@@ -24,9 +24,9 @@ with the cloud controller manager.  The steps are as follows:
 1. Add the `--cloud-provider=external` to the kube-controller-manager config.
 1. Add the `--cloud-provider=external` to the kube apiserver config.
 1. Add the `--cloud-provider=external` to each the kubelet's config.
-1. Add the tag kubernetes.io/cluster/your_cluster_id=owned (if resources are
+1. Add the tag `kubernetes.io/cluster/your_cluster_id=owned` (if resources are
    owned and managed by the cluster) or
-   kubernetes.io/cluster/your_cluster_id=shared (if resources are shared
+   `kubernetes.io/cluster/your_cluster_id=shared` (if resources are shared
    between clusters, and should not be destroyed if the cluster is destroyed)
    to your instances.
 1. Apply the kustomize configuration: `kubectl apply -k
@@ -45,7 +45,7 @@ Follow the detailed steps in [the documentation](https://kubernetes.io/docs/task
 |------|-----------|-------------|
 | kube-apiserver | `--cloud-provider=external` | Disables the cloud provider in the API Server. This will disable the cloud provider code in the kube apiserver, which is limited to the persistent volume labelling controller.  |
 | kube-controller-manager | `--cloud-provider=external` | Disables the cloud provider in the Kube Controller Manager. This disables cloud related control loops, including the route controller, the service controller, and the node lifecycle controller. |
-| kube-controller-manager | --leader-elect=true | Enable leader election  |
+| kube-controller-manager | `--leader-elect=true` | Enable leader election  |
 | kube-controller-manager | `--external-cloud-volume-plugin=aws` | Tells the Kube Controller Manager to run the volume loops that have cloud provider code in them.  This is required for volumes to work if you are not using CSI with migration enabled. |
 | kubelet | `--cloud-provider=external` | Disables the cloud provider in the Kubelet. This disables the built-in kubelet image credential provider, so in order for the kubelet to fetch from ECR repositories, it will need the external ECR kubelet image credential provider binary.  This also disables the EBS attacher interface implementation, which is generally safe as long as the EBS CSI driver is installed and CSI migration is enabled.|
 | aws-cloud-controller-manager | <code>--cloud-provider=[aws&#124;aws/v2]</code> | Optional.  Selects the legacy cloud-provider or the v2 cloud-provider in the aws-cloud-controller-manager. WARNING: the v2 cloud-provider is in a pre-alpha state. |
@@ -56,4 +56,4 @@ In order to create a cluster using kops, you can try the kops example cluster. R
 
 `make kops-example`
 
-This will create a sample kops cluster with the example configuration, found in [examples/kops-new-cluster](../examples/kops-new-cluster)  The cloud cloud controller manager specific configuration is separate, purely for readability purposes, and can be found in [overlays/cloud-controller-manager](../examples/kops-new-cluster/overlays/cloud-controller-manager).
+This will create a sample kops cluster with the example configuration, found in [examples/kops-new-cluster](https://github.com/kubernetes/cloud-provider-aws/tree/master/examples/kops-new-cluster)  The cloud cloud controller manager specific configuration is separate, purely for readability purposes, and can be found in [overlays/cloud-controller-manager](https://github.com/kubernetes/cloud-provider-aws/tree/master/examples/kops-new-cluster/overlays/cloud-controller-manager).