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

tracker: CRI-O support #16

Open
sghosh151 opened this issue Dec 1, 2019 · 0 comments
Open

tracker: CRI-O support #16

sghosh151 opened this issue Dec 1, 2019 · 0 comments

Comments

@sghosh151
Copy link

Is this a BUG REPORT or FEATURE REQUEST?:
Feature Request

What happened:
With Kubernetes support moving to containerd and cri-o alternatives - need support from under container runtimes in a k8s environment.

Opened a request to the OpenShift team to take a look at CRI-O support for kube-forensics
https://bugzilla.redhat.com/show_bug.cgi?id=1775398

This issue is a placeholder until upstream CRI-O support becomes available.

What you expected to happen:
Able to capture pod state for k8s+crio environments.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • kube-forensics version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

  • PodCheckpoint status:
$ kubectl describe -n forensics-system podcheckpoint <checkpoint-name>
  • controller logs:
$ kubectl logs -n forensics-system <forensics-controller-manager pod>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant