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

time-to-k8s: Benchmark k3d with etcd #12014

Closed
spowelljr opened this issue Jul 19, 2021 · 1 comment
Closed

time-to-k8s: Benchmark k3d with etcd #12014

spowelljr opened this issue Jul 19, 2021 · 1 comment
Assignees
Labels
kind/improvement Categorizes issue or PR as related to improving upon a current feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@spowelljr
Copy link
Member

Currently, in the time-to-k8s benchmark, we compare to k3d without etcd. Since both minikube and kind use etcd by default, we should enable etcd in k3d when benchmarking to have a better comparison between the tools.

@spowelljr spowelljr added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/improvement Categorizes issue or PR as related to improving upon a current feature. labels Jul 19, 2021
@spowelljr spowelljr added this to the 1.23.0 milestone Jul 19, 2021
@spowelljr spowelljr self-assigned this Jul 19, 2021
@spowelljr
Copy link
Member Author

spowelljr commented Jul 19, 2021

dqlite was replaced with etcd with k3s-io/k3s#1770 and seems to be used by default.

To confirm I tried the following (multi-node):

% k3d cluster create
INFO[0000] Prep: Network
...
% k3d node create newserver --cluster k3s-default --role server
INFO[0000] Starting Node 'k3d-newserver-0'
% k3d cluster list
NAME          SERVERS   AGENTS   LOADBALANCER
k3s-default   2/2       0/0      true

So from my understanding etcd is being used when benchmarking k3d.

@medyagh @afbjorklund If you think otherwise let me know and I'd be happy to investigate.

Closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement Categorizes issue or PR as related to improving upon a current feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant