sidebar | permalink | keywords | summary |
---|---|---|---|
sidebar |
get-started/acc_operatorhub_install.html |
how to install astra control center, operator, operatorhub, openshift, install astra control center operator, service mesh |
If you use Red Hat OpenShift, you can install the Astra Control Center using an operator. |
If you use Red Hat OpenShift, you can install Astra Control Center using the Red Hat certified operator. Use this procedure to install Astra Control Center from the Red Hat Ecosystem Catalog or using the Red Hat OpenShift Container Platform.
After you complete this procedure, you must return to the installation procedure to complete the remaining steps to verify installation success and log on.
-
Meet environmental prerequisites: Before you begin installation, prepare your environment for Astra Control Center deployment.
TipDeploy Astra Control Center in a third fault domain or secondary site. This is recommended for app replication and seamless disaster recovery. -
Ensure healthy cluster operators and API services:
-
From your OpenShift cluster, ensure all cluster operators are in a healthy state:
oc get clusteroperators
-
From your OpenShift cluster, ensure all API services are in a healthy state:
oc get apiservices
-
-
Ensure a routable FQDN: The Astra FQDN you plan to use can be routed to the cluster. This means that you either have a DNS entry in your internal DNS server or you are using a core URL route that is already registered.
-
Obtain OpenShift permissions: You’ll need all necessary permissions and access to the Red Hat OpenShift Container Platform to perform the installation steps described.
-
Configure a cert manager: If a cert manager already exists in the cluster, you need to perform some prerequisite steps so that Astra Control Center does not install its own cert manager. By default, Astra Control Center installs its own cert manager during installation.
-
Set up Kubernetes ingress controller: If you have a Kubernetes ingress controller that manages external access to services, such as load balancing in a cluster, you need to set it up for use with Astra Control Center:
-
Create the operator namespace:
oc create namespace netapp-acc-operator
-
Complete setup for your ingress controller type.
-
-
(ONTAP SAN driver only) Enable multipath: If you are using an ONTAP SAN driver, be sure that multipath is enabled on all your Kubernetes clusters.
You should also consider the following:
-
Get access to the NetApp Astra Control image registry:
-
Install a service mesh for secure communications: It is strongly recommended that Astra Control host cluster communications channels be secured using a supported service mesh.
ImportantIntegrating Astra Control Center with a service mesh can only be done during Astra Control Center installation and not independent of this process. Changing back from a meshed to an unmeshed environment is not supported. For Istio service mesh use, you’ll need to do the following:
-
Add an
istio-injection:enabled
label to the Astra namespace prior to deploying Astra Control Center. -
Use the
Generic
ingress setting and provide an alternative ingress for external load balancing. -
For Red Hat OpenShift clusters, you’ll need to define
NetworkAttachmentDefinition
on all associated Astra Control Center namespaces (netapp-acc-operator
,netapp-acc
,netapp-monitoring
for application clusters, or any custom namespaces that have been substituted).cat <<EOF | oc -n netapp-acc-operator create -f - apiVersion: "k8s.cni.cncf.io/v1" kind: NetworkAttachmentDefinition metadata: name: istio-cni EOF cat <<EOF | oc -n netapp-acc create -f - apiVersion: "k8s.cni.cncf.io/v1" kind: NetworkAttachmentDefinition metadata: name: istio-cni EOF cat <<EOF | oc -n netapp-monitoring create -f - apiVersion: "k8s.cni.cncf.io/v1" kind: NetworkAttachmentDefinition metadata: name: istio-cni EOF
-
Important
|
Do not delete the Astra Control Center operator (for example, kubectl delete -f astra_control_center_operator_deploy.yaml ) at any time during Astra Control Center installation or operation to avoid deleting pods.
|
If you are planning to push the Astra Control Center bundle to your local registry, you need to use the NetApp Astra kubectl command line plugin.
Complete these steps to install the most recent NetApp Astra kubectl command line plugin.
NetApp provides plugin binaries for different CPU architectures and operating systems. You need to know which CPU and operating system you have before you perform this task.
If you already have the plugin installed from a previous installation, make sure you have the latest version before completing these steps.
-
List the available NetApp Astra kubectl plugin binaries, and note the name of the file you need for your operating system and CPU architecture:
NoteThe kubectl plugin library is part of the tar bundle and is extracted into the folder kubectl-astra
.ls kubectl-astra/
-
Move the correct binary into the current path and rename it to
kubectl-astra
:cp kubectl-astra/<binary-name> /usr/local/bin/kubectl-astra
-
Complete one of the following procedures to access the operator install page:
Red Hat OpenShift web consoleRed Hat Ecosystem Catalog-
Select the NetApp Astra Control Center operator.
-
Select Deploy and use.
-
-
Complete the Install Operator page and install the operator:
NoteThe operator will be available in all cluster namespaces. -
Select the operator namespace or
netapp-acc-operator
namespace will be created automatically as part of the operator installation. -
Select a manual or automatic approval strategy.
NoteManual approval is recommended. You should only have a single operator instance running per cluster. -
Select Install.
NoteIf you selected a manual approval strategy, you’ll be prompted to approve the manual install plan for this operator.
-
-
From the console, go to the OperatorHub menu and confirm that the operator installed successfully.
-
From the console within the Astra Control Center tab of the Astra Control Center operator, select Create AstraControlCenter.
-
Complete the
Create AstraControlCenter
form field:-
Keep or adjust the Astra Control Center name.
-
Add labels for the Astra Control Center.
-
Enable or disable Auto Support. Retaining Auto Support functionality is recommended.
-
Enter the Astra Control Center FQDN or IP address. Do not enter
http://
orhttps://
in the address field. -
Enter the Astra Control Center version; for example, 24.02.0-69.
-
Enter an account name, email address, and admin last name.
-
Choose a volume reclaim policy of
Retain
,Recycle
, orDelete
. The default value isRetain
. -
Select the scale size of the installation.
NoteBy default, Astra will use High Availability (HA) scaleSize
ofMedium
, which deploys most services in HA and deploys multiple replicas for redundancy. WithscaleSize
asSmall
, Astra will reduce the number of replicas for all services except for essential services to reduce consumption. -
-
Generic (
ingressType: "Generic"
) (Default)Use this option when you have another ingress controller in use or would prefer to use your own ingress controller. After Astra Control Center is deployed, you’ll need to configure the ingress controller to expose Astra Control Center with a URL.
-
AccTraefik (
ingressType: "AccTraefik"
)Use this option when you would prefer not to configure an ingress controller. This deploys the Astra Control Center
traefik
gateway as a Kubernetes "LoadBalancer" type service.Astra Control Center uses a service of the type "LoadBalancer" (
svc/traefik
in the Astra Control Center namespace), and requires that it be assigned an accessible external IP address. If load balancers are permitted in your environment and you don’t already have one configured, you can use MetalLB or another external service load balancer to assign an external IP address to the service. In the internal DNS server configuration, you should point the chosen DNS name for Astra Control Center to the load-balanced IP address.NoteFor details about the service type of "LoadBalancer" and ingress, refer to Requirements.
-
-
In Image Registry, use the default value unless you configured a local registry. For a local registry, replace this value with the local image registry path where you pushed the images in a previous step. Do not enter
http://
orhttps://
in the address field. -
If you use an image registry that requires authentication, enter the image secret.
NoteIf you use a registry that requires authentication, create a secret on the cluster. -
Enter the admin first name.
-
Configure resources scaling.
-
Provide the default storage class.
NoteIf a default storage class is configured, ensure that it is the only storage class that has the default annotation. -
Define CRD handling preferences.
-
-
Select the YAML view to review the settings you have selected.
-
Select
Create
.
If you use a registry that requires authentication, create a secret on the OpenShift cluster and enter the secret name in the Create AstraControlCenter
form field.
-
Create a namespace for the Astra Control Center operator:
oc create ns [netapp-acc-operator or custom namespace]
-
Create a secret in this namespace:
oc create secret docker-registry astra-registry-cred -n [netapp-acc-operator or custom namespace] --docker-server=[your_registry_path] --docker username=[username] --docker-password=[token]
NoteAstra Control supports Docker registry secrets only. -
Complete the remaining fields in the Create AstraControlCenter form field.
Complete the remaining steps to verify that Astra Control Center installed successfully, set up an ingress controller (optional), and log in to the UI. Additionally, you’ll need to perform setup tasks after completing installation.