Skip to content
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

KubeEdge Counter Demo is not working properly #65

Closed
zhangyang1997 opened this issue Sep 14, 2020 · 7 comments
Closed

KubeEdge Counter Demo is not working properly #65

zhangyang1997 opened this issue Sep 14, 2020 · 7 comments

Comments

@zhangyang1997
Copy link

zhangyang1997 commented Sep 14, 2020

What happened:
KubeEdge Counter Demo is not working properly
What you expected to happen:
use [kubectl get pods -o wide] can get ke-edge1's IP and use [docker logs -f counter-container-id] can get count value.

Environment:

  • KubeEdge version(e.g. cloudcore/edgecore --version): v1.4.0
    CloudSide Environment:
  • Hardware configuration (e.g. lscpu):Intel(R) Xeon(R) Gold 6126 CPU @ 2.60GHz
  • OS (e.g. cat /etc/os-release):centos8
  • Kernel (e.g. uname -a):Linux ke-cloud 4.18.0-193.el8.x86_64 Added demo for LED light with raspberry Pi #1 SMP Fri May 8 10:59:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  • Go version (e.g. go version): go version go1.14.4 linux/amd64
  • Others:

EdgeSide Environment:

  • edgecore version (e.g. edgecore --version):v1.4.0
  • Hardware configuration (e.g. lscpu):Intel(R) Xeon(R) Gold 6126 CPU @ 2.60GHz
  • OS (e.g. cat /etc/os-release):centos8
  • Kernel (e.g. uname -a):Linux ke-edge1 4.18.0-193.el8.x86_64 Added demo for LED light with raspberry Pi #1 SMP Fri May 8 10:59:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  • Go version (e.g. go version): go version go1.14.4 linux/amd64
  • Others:

p1
p2
p3
p4
p5

@dejavu6
Copy link

dejavu6 commented Oct 27, 2020

请问怎么解决的,我遇到一样的问题了

@zhangyang1997 zhangyang1997 reopened this Oct 27, 2020
@bluntWu
Copy link

bluntWu commented Dec 11, 2020

edit /etc/kubernetes/manifests/kube-apiserver.yaml
--insecuret-port=8080
--insecure-bind-address=0.0.0.0
restart

@swartz-k
Copy link

swartz-k commented Dec 11, 2020

the quickesty way, i think; file: examples/kubeedge-counter-demo/web-controller-app/utils/kubeclient.go should be edit like this

// replace this with the K8s Master IP
var KubeMaster = "https://192.68.105.207:6443"
var Kubeconfig = "/static/admin.conf"

and copy admin.conf to your container;fileexamples/kubeedge-counter-demo/web-controller-app/Dockerfile add line

COPY admin.conf /static 

the better way is get permission by clusterrole && clusterrolebinding && serviceaccount,and also i think this demo has a better way to update CR,if i will solve those problems,i will share it

@DapengLan
Copy link

edit /etc/kubernetes/manifests/kube-apiserver.yaml
--insecuret-port=8080
--insecure-bind-address=0.0.0.0
restart

I got the issue that the port is in use by the Kube-api. any suggestions? thanks

2020/12/11 13:22:23 Get kubeConfig successfully
2020/12/11 13:22:23 Get crdClient successfully
2020/12/11 13:22:24.001 [I] http server Running on http://:8089
2020/12/11 13:22:24.001 [C] ListenAndServe: listen tcp :8089: bind: address already in use

@swartz-k
Copy link

edit /etc/kubernetes/manifests/kube-apiserver.yaml
--insecuret-port=8080
--insecure-bind-address=0.0.0.0
restart

I got the issue that the port is in use by the Kube-api. any suggestions? thanks

2020/12/11 13:22:23 Get kubeConfig successfully
2020/12/11 13:22:23 Get crdClient successfully
2020/12/11 13:22:24.001 [I] http server Running on http://:8089
2020/12/11 13:22:24.001 [C] ListenAndServe: listen tcp :8089: bind: address already in use

maybe you should check deployment,hostNetwork: true i delete it and didn`t get error

@daixiang0
Copy link
Member

Please try the latest example to confirm this issue exists or not, it works at my env, thanks :)

If it still exists, please reopen it!

/close

@kubeedge-bot
Copy link
Collaborator

@daixiang0: Closing this issue.

In response to this:

Please try the latest example to confirm this issue exists or not, it works at my env, thanks :)

If it still exists, please reopen it!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants