✨Document running E2E tests locally #982
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
the
size/L
mdbooth
force-pushed
the
upstream-tests
branch
from
b5131dd to
bad34a9
Compare
| OPENSTACK_CLOUD_CACERT_B64=$(base64 -w /path/to/mycloud-ca.crt) | ||
| ``` | ||
|
|
||
| CAPO deployed in the local kind cluster will automatically pick up a `cacert` defined in your `clouds.yaml` so you will see servers created in OpenStack without specifying `OPENSTACK_CLOUD_CACERT_B64`. However, the cacert won't be deployed to those servers, so kubelet will fail to start. |
There was a problem hiding this comment.
not sure I fully understand this ,the cacert is mostly used for openstack interaction defined in clouds.yaml
so why it's related to kubelet?
There was a problem hiding this comment.
We also need to pass the cacert into the cluster so the cloud provider [1] can talk to OpenStack. If the cloud provider fails to come up then the Node will not become ready and the tests fail.
[1] kubelet in-tree provider, or CCM for external cloud provider
There was a problem hiding this comment.
ok, OCCM need this cacert, thanks for the reminder
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc, mdbooth The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
What this PR does / why we need it:
Documents how to run E2E tests locally, including the enhancements added in #981.