This PR enables the openebs-upgrade to be able to adapt the existing OpenEBS components i.e. if a user has already installed OpenEBS by some means other than openebs-upgrade such as operator.yaml, helm, etc and now the user wants to use openebs-upgrade to manage the OpenEBS components going further such as configuration update, upgrade, etc then the user can create an adoptOpenEBS CR given below which will allow the openebs-upgrade to adopt the existing OpenEBS components and then start managing it going forward.
An example adoptOpenEBS YAML which can be used to adopt the existing OpenEBS components:
# This configuration is for OpenEBS Adoption i.e., this CR will help in triggering
# the adoption of existing OpenEBS configuration via openebs-upgrade.
apiVersion: dao.mayadata.io/v1alpha1
kind: AdoptOpenEBS
metadata:
name: adopt-openebs-1.10.0
# Namespace i.e. the namespace where the OpenEBS components
# have been installed.
namespace: openebs
This PR enables the
openebs-upgradeto be able to adapt the existing OpenEBS components i.e. if a user has already installed OpenEBS by some means other thanopenebs-upgradesuch as operator.yaml, helm, etc and now the user wants to useopenebs-upgradeto manage the OpenEBS components going further such as configuration update, upgrade, etc then the user can create anadoptOpenEBSCR given below which will allow theopenebs-upgradeto adopt the existing OpenEBS components and then start managing it going forward.An example
adoptOpenEBSYAML which can be used to adopt the existing OpenEBS components:Signed-off-by: sagarkrsd sagar.kumar@mayadata.io