-
Notifications
You must be signed in to change notification settings - Fork 36
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
Support customized kubeadm control plane configurations #7
Labels
enhancement
New feature or request
Comments
innobead
changed the title
Support customized kubeadm config
Support customized kubeadm configurations
Aug 16, 2020
innobead
changed the title
Support customized kubeadm configurations
Support customized kubeadm control plane configurations
Sep 12, 2020
➜ ~ kubefire cluster create demo-kubeadm --extra-options="api_server_options='audit-log-maxage=10' controller_manager_options='concurrent-deployment-syncs=10,concurrent-endpoint-syncs=8' scheduler_options='kube-api-burst=101'" |
➜ kubefire (master) ✗ kubefire cluster config demo-kubeadm -o yaml
name: demo-kubeadm
bootstrapper: kubeadm
pubkey: /home/davidko/.kubefire/clusters/demo-kubeadm/key.pub
prikey: /home/davidko/.kubefire/clusters/demo-kubeadm/key
version: v1.19.1
image: ghcr.io/innobead/kubefire-opensuse-leap:15.2
kernel_image: ghcr.io/innobead/kubefire-ignite-kernel:4.19.125-amd64
kernel_args: console=ttyS0 reboot=k panic=1 pci=off ip=dhcp security=apparmor apparmor=1
extra_options:
api_server_options:
- audit-log-maxage=10
controller_manager_options:
- concurrent-deployment-syncs=10
- concurrent-endpoint-syncs=8
scheduler_options:
- kube-api-burst=101
deployed: true
master:
count: 1
memory: 2GB
cpus: 2
disk_size: 10GB
worker:
count: 0
memory: 2GB
cpus: 2
disk_size: 10GB |
innobead
added a commit
that referenced
this issue
Sep 13, 2020
innobead
added a commit
that referenced
this issue
Sep 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There is no way to customize the cluster configurations when deploying with kubeadm.
Describe the solution you'd like
Being able to provision a cluster w/ customized kubeadm configs including control planes and kubelet.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: