EKS PVC Claim

[alongir]

Context:

• Kubeshark support a persistent volume claim as the storage for Workers.
• Having said that, this is is not a simple procedure
• We'd like to make it simple for users, by providing clear instructions how to provision such storage across popular K8s distributions, starting with EKS

Tasks steps:

• Open a new AWS account and add to the Kubeshark organization following a sent invitation
• Start an EKS cluster with at least two nodes.
• Make every effort to reduce the spend by choosing small instances and scaling the cluster down when not in use
• Make all the necessary steps to provision a persistent volume
• Consider using an EFS storage
• Ideally use ReadWriteMany. If not possible, suggest a different method
• Make Kubeshark work with the PVC
• Document the process, so anyone with minimal devops skills can follow the instructions and do it.
• Always use a PR in a dedicated branch, available for review, commenting and approval.

[berezins]

• Cluster https://us-west-1.console.aws.amazon.com/eks/home?region=us-west-1#/clusters/kubeshark-dev
  

• Nodes https://us-west-1.console.aws.amazon.com/eks/home?region=us-west-1#/clusters/kubeshark-dev/nodegroups/kubeshark-dev-micro?selectedTab=nodes
  

[berezins]

Downscaled to 0 nodes when not used by us:

[berezins]

kubeshark/kubeshark#1455

[berezins]

#15

[berezins]

Dynamic provisioning described and added in #17 should work even without this PR kubeshark/kubeshark#1455

[berezins]

All PRs by this task are merged (#15, #16, #17 and kubeshark/kubeshark#1455). So can we close it, @alongir ?

[alongir]

I think it's ready. Waiting for @mertyildiran to take a quick look.