Merge pull request #4220 from binchenX/doc

📖 misc fix for developer doc

Author: k8s-ci-robot

docs/book/src/clusterctl/developers.md

@@ -37,19 +37,20 @@ In order to build artifacts for the CAPI core provider, the kubeadm bootstrap pr
 
 ```
 make docker-build REGISTRY=gcr.io/k8s-staging-cluster-api
-make -C test/infrastructure/docker generate-manifests REGISTRY=gcr.io/k8s-staging-cluster-api
+make generate-manifests REGISTRY=gcr.io/k8s-staging-cluster-api PULL_POLICY=IfNotPresent
 ```
 
 In order to build docker provider artifacts
 
 ```
 make -C test/infrastructure/docker docker-build REGISTRY=gcr.io/k8s-staging-cluster-api
-make -C test/infrastructure/docker generate-manifests REGISTRY=gcr.io/k8s-staging-cluster-api
+make -C test/infrastructure/docker generate-manifests REGISTRY=gcr.io/k8s-staging-cluster-api PULL_POLICY=IfNotPresent
 ```
 
 ### Create a clusterctl-settings.json file
 
-Next, create a `clusterctl-settings.json` file and place it in your local copy of Cluster API. Here is an example:
+Next, create a `clusterctl-settings.json` file and place it in your local copy
+of Cluster API. This file will be used by [create-local-repository.py](#create-the-local-repository). Here is an example:
 
 ```yaml
 {
@@ -131,12 +132,12 @@ please note that each `provider_repo` should have its own `clusterctl-settings.j
 }
 ```
 
-## Create a kind cluster
+## Create a kind management cluster
 
 [kind] can provide a Kubernetes cluster to be used a management cluster.
 See [Install and/or configure a kubernetes cluster] for more about how.
 
-Before running clusterctl init, you must ensure all the required images are available in the kind cluster.
+*Before* running clusterctl init, you must ensure all the required images are available in the kind cluster.
 
 This is always the case for images published in some image repository like docker hub or gcr.io, but it can't be
 the case for images built locally; in this case, you can use `kind load` to move the images built locally. e.g
@@ -150,6 +151,25 @@ kind load docker-image gcr.io/k8s-staging-cluster-api/capd-manager-amd64:dev
 
 to make the controller images available for the kubelet in the management cluster.
 
+When the kind cluster is ready and all the required images are in place, run
+the clusterctl init command generated by the create-local-repository.py
+script.
+
+Optionally, you may want to check if the components are running properly. The
+exactly components are depend on which providers you have initialized, below
+is an example output with docker provider being installed.
+
+```
+kubectl get deploy -A | grep  "cap\|cert"
+capd-system                         capd-controller-manager                         1/1     1            1           25m
+capi-kubeadm-bootstrap-system       capi-kubeadm-bootstrap-controller-manager       1/1     1            1           25m
+capi-kubeadm-control-plane-system   capi-kubeadm-control-plane-controller-manager   1/1     1            1           25m
+capi-system                         capi-controller-manager                         1/1     1            1           25m
+cert-manager                        cert-manager                                    1/1     1            1           27m
+cert-manager                        cert-manager-cainjector                         1/1     1            1           27m
+cert-manager                        cert-manager-webhook                            1/1     1            1           27m
+```
+
 ## Additional Notes for the Docker Provider
 
 ### Select the appropriate kubernetes version