Skip to content

Enhancements to sysbox-deploy-k8s #533

Open
Open
Enhancements to sysbox-deploy-k8s#533
Labels
EpicEpic
Milestone
v0.6

Description

@ctalledo
ctalledo
opened on Apr 15, 2022

The following enhancements to sysbox-deploy-k8s are needed (as of 04/15/22):

  1. Add K8s 1.22 & 1.23 support.
  2. Add support for systemd-managed cgroups.
  3. Add a way to configure sysbox-deploy-k8s (e.g., via K8s config map).
  4. Handle scenarios where host uses mutliple kubelet systemd drop-in files (issue k8s-daemonset-installer breaks in scenarios with multiple kubelet systemd drop-in files #525).
  5. Handle installation behind HTTPS proxy (issue Sysbox kubernetes install fails behind HTTPS Proxy #522).
  6. Have the sysbox-deploy-k8s daemonset monitor the kernel version periodically and if it detects changes, reinstall shiftfs with the appropriate version
  7. Handle scenario where CRI-O is already installed in cluster.
  8. Handle single-node clusters (i.e,. currently sysbox-deploy-k8s requires >= 2 nodes).
  9. Create a Helm chart for sysbox-deploy-k8s.
  10. Add support for more host distros (e.g., Debian, RedHat, Fedora, CentOS-Stream, etc.)

Activity

  1. ctalledo
    added
    EpicEpic
    on Apr 15, 2022
  2. ctalledo
    added this to the v0.6 milestone on Apr 15, 2022

  3. samcday commented on Apr 17, 2022

    @samcday
    samcday
    on Apr 17, 2022

    Is this list sorted by "most important first"? :) If so, great! I came to this issue tracker to voice interest in Kube >1.21 support.

    1.20 is already EOL and 1.21 will meet the same fate in about 2 months. (I'm particularly interested in 1.22 for the alpha apiserver tracing support).

    I introduced Sysbox CE at my $dayjob to allow us to cohabitate some CI workloads alongside non-CI workloads in our baremetal clusters. It's working great, thanks! If a release candidate rolls around with Kube 1.22 support, I have access to a few 1.22+ baremetal clusters to test it on.

  4. rodnymolina commented on Apr 17, 2022

    @rodnymolina
    rodnymolina
    on Apr 17, 2022
    Member

    @samcday, thanks for the feedback!

    I don't think the list is necessarily sorted based on priorities, but 1.22 support is certainly one of the most important issues for us to tackle.

    Btw, we just addressed 2) and 6) in the last few hours and planning to jump into 1), 4) and 5) right after.

  5. felipecrs commented on May 4, 2022

    @felipecrs
    felipecrs
    on May 4, 2022
    Contributor

    The 9 will help to streamline the installation, upgrade, and uninstallation of Sysbox on K8s. It will be nice! :)

  6. felipecrs commented on May 4, 2022

    @felipecrs
    felipecrs
    on May 4, 2022
    Contributor

    Here is a good starting point, btw: https://github.com/helm/charts-repo-actions-demo

  7. immae1 commented on Aug 26, 2022

    @immae1
    immae1
    on Aug 26, 2022

    @rodnymolina  @ctalledo hey - what's the current state about k8s 1.22.x support? I'm asking because we wanna use sysbox inside of AKS an MS deprecated 1.21.X. Thx in advance for your answer :)

  8. ctalledo commented on Aug 26, 2022

    @ctalledo
    ctalledo
    on Aug 26, 2022
    MemberAuthor

    Hi @immae1, support for v1.22 and v1.23 is there already.

    Apologies, forgot to update this issue accordingly, will do so now.

  9. rodnymolina commented on Aug 29, 2022

    @rodnymolina
    rodnymolina
    on Aug 29, 2022
    Member

    Please see here for our official doc on this matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EpicEpic

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions