K3s the right approach for configuration

  • Hi


    I am continuing testing of k3s plugin and I am wondering about the below cases:

    1. Separate location of k3s (/var/lib/rancher) by moving it to another disk/ device (for example to reduce write noise). Now, the location is placed on rootfs and it cannot be moved to specific device. When I think about symliks, it will huge probability, it will be not ready before start k3s (for example source location not encrypted and not mounted), so the location /var/lib/rancher will be overwritten by k3s itself. Does available the right approach for this case without generate issues for plugin (custom settings which will be replaced later during deployment/re-deplyment/upgrade etc)?

    2. Custom address subnets for kubernetes pods and services because of conflicts with real networks. Does it possible to change it without generate issues for plugin architecture?

    3. Does it possible to reduce writing to sqlite database for k3s (now it is around 0,5gb/ 24h)?

  • macom

    Approved the thread.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!