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.

Sign up for GitHub

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

Jump to bottom

Use CRI to obtain pod sandbox IDs instead of Kubernetes API (#714) #741

Merged
merged 1 commit into from
Dec 5, 2019
Merged

Use CRI to obtain pod sandbox IDs instead of Kubernetes API (#714) #741

merged 1 commit into from
Dec 5, 2019

Commits on Dec 4, 2019

  1. Use CRI to obtain pod sandbox IDs instead of Kubernetes API (aws#714) 

    * Revert "fix: get container ID from kube rather than docker (aws#371)"

This reverts commit 14de538.

* go mod tidy

* Add initial proof-of-concept implementation of CRI support.

* Update CRI socket path to /var/run/cri.sock

* Filter ready sandboxes and abort if there's a pod UID conflict.

* Revert "fix: get container ID from kube rather than docker (aws#371)"

This reverts commit 14de538.

* Address review comments, refactor to use pod sandbox nomenclature consistently.

* Bail if we can't retrieve local pod sandboxes on startup.
    @drakedevel
    drakedevel authored and Claes Mogren committed Dec 4, 2019
    Configuration menu
    Copy the full SHA
    d9a4c62 View commit details
    Browse the repository at this point in the history