| 최신판 |
당신의 편집 |
| 20번째 줄: |
20번째 줄: |
|
| |
|
| ===컨테이너 레지스트리=== | | ===컨테이너 레지스트리=== |
| If you’re using kind, you’ll need a way to push your images to a registry so they can be pulled. You can instead side-load all images, but the registry workflow is lower-friction.
| |
|
| |
| Most users test with GCR, but you could also use something like Docker Hub. If you choose not to use GCR, you’ll need to set the REGISTRY environment variable.
| |
|
| |
| ===Kustomize=== | | ===Kustomize=== |
| You’ll need to install kustomize. There is a version of kustomize built into kubectl, but it does not have all the features of kustomize v3 and will not work.
| |
|
| |
| ===Kubebuilder=== | | ===Kubebuilder=== |
| You’ll need to install kubebuilder.
| |
|
| |
| ===Envsubst=== | | ===Envsubst=== |
| You’ll need envsubst or similar to handle clusterctl var replacement. Note: drone/envsubst releases v1.0.2 and earlier do not have the binary packaged under cmd/envsubst. It is available in Go pseudo-version v1.0.3-0.20200709231038-aa43e1c1a629
| |
|
| |
| We provide a make target to generate the envsubst binary if desired. See the provider contract for more details about how clusterctl uses variables.
| |
|
| |
|
| |
| make envsubst
| |
| The generated binary can be found at ./hack/tools/bin/envsubst
| |
|
| |
| ===Cert-Manager=== | | ===Cert-Manager=== |
| You’ll need to deploy cert-manager components on your management cluster, using kubectl
| |
|
| |
|
| |
| kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.4/cert-manager.yaml
| |
| Ensure the cert-manager webhook service is ready before creating the Cluster API components.
| |
|
| |
| This can be done by following instructions for manual verification from the cert-manager web site. Note: make sure to follow instructions for the release of cert-manager you are installing.
| |
|
| |
|
| ==개발== | | ==개발== |
