-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Cloud Native Storage and refactoring with a new Kubernetes provider #342
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
Signed-off-by: Nicolas Lamirault <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, what's different between k8s and kubernetes?
@mingrammer it is to differentiate the ecosystem of Kubernetes applications (Rook, Velero, ....) from internal Kubernetes applications (Deployment, Ingress, ...) |
How do think about move these tools under |
@mingrammer i will do that. |
Yep. |
Hey folks, |
Refactoring Kubernetes ecosystem into a new Kubernetes provider: to use
<provider>/<type>/resource
, and not<provider>/<type>/<subcategory>/resource
Add Cloud Native storage :