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

Plugin shell execute on: role=master, but execute on all node #795

Closed
init-object opened this issue Oct 28, 2021 · 4 comments · Fixed by #799
Closed

Plugin shell execute on: role=master, but execute on all node #795

init-object opened this issue Oct 28, 2021 · 4 comments · Fixed by #799
Labels
kind/bug Something isn't working

Comments

@init-object
Copy link
Contributor

What happened:

image

image
在master机器上修改kube-apiserver.yaml 文件 调整nodeport范围
在node机器上也执行了shell脚本

What you expected to happen:

只在master节点上执行shell脚本

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • sealer version (use sealer version): v0.5.1
  • Cloud provider or hardware configuration: 4 core 8g
  • OS (e.g: cat /etc/os-release): CentOS Linux 7 (Core)
  • Kernel (e.g. uname -a):Linux k8s-master01 3.10.0-1127.el7.x86_64 fix: ci lint for mod registry and image #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools:
  • Others:
@init-object init-object added the kind/bug Something isn't working label Oct 28, 2021
@bxy4543
Copy link
Member

bxy4543 commented Oct 28, 2021

currently not supports , use on: 192.168.1.2,192.168.1.1,192.168.1.3 instead of specified ip.

@fanux
Copy link
Collaborator

fanux commented Oct 29, 2021

If you want to define your own apiserver config, The better way is using constomized kubeadm config. #762 check this out.

@fanux fanux closed this as completed in #799 Nov 2, 2021
@init-object

This comment has been minimized.

@init-object
Copy link
Contributor Author

init-object commented Nov 2, 2021

If you want to define your own apiserver config, The better way is using constomized kubeadm config. #762 check this out.
image
image
image
I try to use the apiserver config defined by myself but it doesn't take effect

I know the reason, because the sealer machine and the k8s-master0 machine are not the same machine. the rootfs folder is not mounted on the machine where the sealer is executed
I think this is a bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants