forked from openebs/website
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request openebs#189 from rakeshPRaghu/importAdditionalInfo
(docs) : importing additional info from docs.openebs.io (2.11.0)
- Loading branch information
Showing
10 changed files
with
2,650 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
41 changes: 41 additions & 0 deletions
41
docs/versioned_docs/version-2.11.0/additional-info/alphafeatures.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
id: alphafeatures | ||
title: Alpha Features | ||
--- | ||
|
||
This page provides an overview of OpenEBS components and features presently in Alpha version and under active development. These features are not recommended to be used in production. We suggest you to familiarize and try these features on test clusters and reach out to [OpenEBS Community](/introduction/community) if you have any queries, feedback or need help on these features. | ||
|
||
The list of alpha features include: | ||
- [CSI Driver for Local PV - Device](#csi-driver-for-local-pv-device) | ||
- [Dynamic NFS Provisioner](#dynamic-nfs-provisioner) | ||
- [OpenEBS CLI](#openebs-cli) | ||
- [OpenEBS Monitoring Add-on](#openebs-monitoring-add-on) | ||
|
||
:::note | ||
Upgrade is not supported for features in Alpha version. | ||
::: | ||
|
||
## CSI Driver for Local PV - Device | ||
|
||
OpenEBS is developing a CSI driver for provisioning Local PVs that are backed by block devices. | ||
|
||
For additional details and detailed instructions on how to get started with OpenEBS Local PV - Device CSI Driver please refer this [Quickstart guide](https://github.com/openebs/device-localpv). | ||
|
||
|
||
## Dynamic NFS Provisioner | ||
|
||
OpenEBS is developing a dynamic NFS PV provisioner that can setup a new NFS server on top of any block storage. | ||
|
||
For additional details and detailed instructions on how to get started with OpenEBS NFS PV provisioner please refer this [Quickstart guide](https://github.com/openebs/dynamic-nfs-provisioner). | ||
|
||
## OpenEBS CLI | ||
|
||
OpenEBS is developing a kubectl plugin for openebs called `openebsctl` that can help perform administrative tasks on OpenEBS volumes and pools. | ||
|
||
For additional details and detailed instructions on how to get started with OpenEBS CLI please refer this [Quickstart guide](https://github.com/openebs/openebsctl). | ||
|
||
## OpenEBS Monitoring Add-on | ||
|
||
OpenEBS is developing a monitoring add-on package that can be installed via helm or kubectl for setting up a default prometheus, grafana and alert manager stack. The package also will include default service monitors, dashboards and alert rules. | ||
|
||
For additional details and detailed instructions on how to get started with OpenEBS Monitoring Add-on please refer this [Quickstart guide](https://github.com/openebs/monitoring). |
661 changes: 661 additions & 0 deletions
661
docs/versioned_docs/version-2.11.0/additional-info/faq.md
Large diffs are not rendered by default.
Oops, something went wrong.
20 changes: 20 additions & 0 deletions
20
docs/versioned_docs/version-2.11.0/additional-info/k8supgrades.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
id: k8supgrades | ||
title: Best practices to follow when upgrading Kubernetes | ||
sidebar_label: Kubernetes upgrades | ||
--- | ||
|
||
There are few reasons why nodes in a Kubernetes cluster get rebooted | ||
|
||
- Kubernetes upgrades do need to happen to new features that roll out and to get minimum requirements satisfied for the applications upgrade running on Kubernetes. The upgrade process of Kubernetes cluster involves upgrading the nodes one by one. This process may involve rebooting of the nodes of the cluster. | ||
- Kubernetes nodes go through hardware changes | ||
|
||
### Volume replica quorum requirement | ||
|
||
In either case, when the nodes are rebooted, the OpenEBS volume targets lose access to the replicas hosted on that node. OpenEBS volume replicas need to be in quorum for the volume to be online. When a Kubernetes node is rebooted, and the node comes back online, the rebuilding process of the volume replicas may take few minutes. If the other node is rebooted before the volume replicas are completely rebuilt, the volume replicas may loose quorum and the corresponding volumes may be marked read-only, which results in the unavailability of data to the application. | ||
|
||
It is recommended that before a Kubernetes node is rebooted, make sure all the replicas of all OpenEBS volumes are healthy/online and there is no rebuild process is ongoing. | ||
|
||
## See Also: | ||
|
||
[Seeking help](/introduction/community) |
Oops, something went wrong.