Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

Add documentation for k8s executor with privileged container #42469

Closed

Description

@eseliger

Today, we do not have an optimal way of deploying executors to Kubernetes. We have work arounds for customers to be able to deploy executors.

Done

  • Document how to deploy executors to Kubernetes
  • Document security expectations

Activity

  1. self-assigned this
    on Oct 4, 2022
  2. eseliger commented on Oct 4, 2022

    @eseliger
    MemberAuthor

    Potentially also do that for docker compose.

  3. eseliger commented on Oct 5, 2022

    @eseliger
    MemberAuthor

    https://github.com/sourcegraph/sourcegraph/issues/36839
    https://github.com/sourcegraph/sourcegraph/issues/36838
    sourcegraph/deploy-sourcegraph-docker#826
    sourcegraph/deploy-sourcegraph#4140

    One thing to find out: K8s 1.24+ doesn’t support docker anymore. So in my understanding it’s not docker-in-docker, it’s containerd that you could access as a privileged container .. and executor and src-cli don’t support contained today.
    So.. maybe this would only work on k8s clusters < 1.24, and beyond that we would have to support containerd as a runtime.

  4. removed their assignment
    on Oct 5, 2022
  5. eseliger commented on Nov 12, 2022

    @eseliger
    MemberAuthor

    I think this could also be useful for an initial E2E test.

  6. self-assigned this
    on Jan 17, 2023
  7. davejrt commented on Jan 19, 2023

    @davejrt
    Contributor

    @eseliger do we actually have the workaround published (without current docs)? I have a rough deployment for an executor working in k8s now we could use that I publish and document

  8. eseliger commented on Jan 20, 2023

    @eseliger
    MemberAuthor

    The only stuff we have on this topics lives in the comments and PRs in these tickets https://github.com/sourcegraph/sourcegraph/issues/42469#issuecomment-1268160825

    I want to reiterate that we rely on being able to speak to the underlying docker daemon on the k8s node machines, and that kubernetes by default (and in a bunch of standard deployments, too) does not actually use docker but containerd, which is not a supported backend today afaik.

    Hope that helps, and we should be careful how we document this as it is relatively brittle and relies on a bunch of assumptions to the deployment of k8s!

  9. Piszmog commented on Feb 21, 2023

    @Piszmog
    Contributor

    Closing as the PR has been merged

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions