rewording for mvk
This commit is contained in:
parent
fc7ff3c260
commit
a21c403a8c
1 changed files with 3 additions and 3 deletions
|
|
@ -21,17 +21,17 @@ Responding to these challenging scenarios, Minimal Viable Kubernetes (MVK) provi
|
|||
|
||||
MVK helps create a minimal K8s setup and one which is a viable implementation of Kubernetes. Initially this may be used for test and development work, but extending this into production is also its goal.
|
||||
|
||||
Typical use cases of MVK are aimed toward entirely self hosted environments. This may be entirely outside of any managed Kubernetes or cloud platform, which are often as not proprietary in their design and provisioning of k8s.
|
||||
Typical use cases of MVK are aimed toward entirely self hosted environments. This may be outside of any managed Kubernetes or cloud platform, which are often as not proprietary in their design and provisioning of k8s.
|
||||
|
||||
The goals of MVK are to increase portability and reduce 'vendor lock in'.
|
||||
|
||||
It can also reduce costs, provided that its users are already, or become, familiar with Kubernetes and its day to day operational and management.
|
||||
|
||||
*We think that everyone should know more about Kubernetes*.
|
||||
*We think that **everyone** should know more about Kubernetes*.
|
||||
|
||||
A greater understanding of k8s results in us all becoming less reliant on others providing this as a service for us. It protects our industry from losing these skills entirely.
|
||||
|
||||
_Above all it can help us to gain control over our digital sovereignty._
|
||||
**Above all it can help us to gain control over our digital sovereignty.**
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue