InfoScale™ 9.0 Support for Containers - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Arctera InfoScale™ on OpenShift
- Installing Arctera InfoScale™ on Kubernetes
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing InfoScale DR on OpenShift
- Installing InfoScale DR on Kubernetes
- TECHNOLOGY PREVIEW: Disaster Recovery scenarios
- Configuring InfoScale
- Troubleshooting
Installing the Special Resource Operator
You must install a Special Resource Operator (SRO) first, before installing Arctera InfoScale™. After the SRO is installed on the system, InfoScale can be deployed.
Download
YAML.tar
from the Arctera Download Center.Untar
YAML.tar
.After you untar
YAML.tar
, the folders/YAML/OpenShift/
,/YAML/DR
, and/YAML/Kubernetes
are created. Each folder contains files required for installation.On a Kubernetes cluster -
Run kubectl create -f /YAML/Kubernetes/sro.yaml on the master node to install the Special Resource Operator (SRO) .
Review output as under.
namespace/openshift-special-resource-operator created customresourcedefinition.apiextensions.k8s.io/ specialresources.sro.openshift.io created serviceaccount/special-resource-controller-manager created role.rbac.authorization.k8s.io/ special-resource-leader-election-role created clusterrole.rbac.authorization.k8s.io/ special-resource-manager-role created clusterrole.rbac.authorization.k8s.io/ special-resource-metrics-reader created clusterrole.rbac.authorization.k8s.io/ special-resource-proxy-role created rolebinding.rbac.authorization.k8s.io/ special-resource-leader-election-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/ special-resource-manager-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/ special-resource-proxy-rolebinding created configmap/special-resource-dependencies created configmap/special-resource-lifecycle created service/special-resource-controller-manager-metrics-service created deployment.apps/special-resource-controller-manager created
Run kubectl create -f /YAML/Kubernetes/sr.yaml on the master node to create Special Resource.
Review output as under.
specialresource.sro.openshift.io/special-resource-preamble created
Run the following commands and review the output to verify whether SR creation and SRO installation is successful.
kubectl get SpecialResource
Output similar to the following indicates a successful installation.
NAME AGE special-resource-preamble 2m24s
kubectl get pods -n openshift-special-resource-operator
Output similar to the following indicates a successful installation.
NAME READY STATUS RESTARTS AGE special-resource-controller-manager 1/1 Running 0 2m35s -66c8fc64b5-9wv6l
Note:
The name in the output here is used in the following command.
kubectl logs special-resource-controller-manager-66c8fc64b5-9wv6l -n openshift-special-resource-operator -c manager
Output similar to the following indicates a successful installation.
<timestamp> INFO status RECONCILE SUCCESS: Reconcile