-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add local-up.sh #26
Add local-up.sh #26
Conversation
wait this kubeedge/kubeedge#2495 to merged. |
aba02dd
to
236ecfc
Compare
Now since we builds images locally, we only can start gm at edgenode(at which edgecore running locally). TODO: deploy gm to test-control-plane master node which are created by kind . Found a way to deploy gm image to test-control-plane : kubernetes-sigs/cri-tools#546.
|
with setsid command, we can handle our cleanups before cleanup kubeedge. |
4b2cb6c
to
f2d1d99
Compare
just use |
5f3144a
to
dacc80d
Compare
1b7f10f
to
567c2a3
Compare
567c2a3
to
5a5eacc
Compare
|
5a5eacc
to
e3d7da9
Compare
Developers can run `hack/local-up.sh` to setup up a local environment including: 1. a local k8s cluster with a master node. 2. a kubeedge node. 3. our gm/lc. Based on the kubeedge-local-up script which builds a local k8s cluster and kubeedge, our local-up script installs our package locally for simply developing and preparing for e3e tests. It does: 1. build the gm/lc/worker images. 2. download kubeedge source code and run its localup script. 3. prepare our k8s env. 4. config gm config and start gm. 5. start lc. 6. add cleanup For cleanup, it needs to do our cleanups before kubeedge cleanup otherwise lc cleanup (via kubectl delete) is stuck and lc container is kept running.
e3d7da9
to
f39181a
Compare
Developers can run
hack/local-up.sh
to setup up a local environmentincluding:
Based on the kubeedge-local-up script which builds a local k8s cluster
and kubeedge, our local-up script installs our package locally for
simply developing and preparing for e3e tests.
It does:
For cleanup, it needs to do our cleanups before kubeedge cleanup
otherwise lc cleanup (via kubectl delete) is stuck and lc container is
kept running.