4.5 Creating the Management Container

Run the installManagementContainer.sh script to create the Management Container.

1. On the node where you downloaded the installation files, navigate to the $WORKDIR/oaaimages/oaa-install directory:

   cd $WORKDIR/oaaimages/oaa-install

2. Run the installManagementContainer.sh script with arguments. For example:

   ./installManagementContainer.sh -t ./<oaa-image>.tar

   A full list of arguments for installManagementContainer.sh is shown in the table below:

   Command line argument	Mandatory	Description
   -t	No	Path to the OAA image tar file. Usage: If not provided pull, tag, and push to the Container Image Registry will not be performed. If pull, tag, and push is required the path to the image <oaa-image.tar> must be provided, for example: -t ./oaa-latest.tar. The install script will first attempt to use podman to perform this task, and if not found will use Docker if available. If neither podman nor Docker are available the script will exit.
   -c	No	Path to OAA management helm chart. If not provided the script will use ./charts/oaa-mgmt as the path.
   -d	No	Perform a helm dry-run of the installation.
   -f	No	Path to installOAA.properties. If not provided ./installOAA.properties will be used.
   -v	No	Runs the script in verbose mode.
   -p	No	Set http/https proxies in the OAA management container's environment. By default the proxies will not be set. If specified the script will use its environment to find the proxy configuration to use.
   -e	No	Add entries to OAA management container's /etc/hosts. By default entries are not added. If specified the script will prompt for the information.
   -n	No	Do not prompt By default the script will prompt for the information it needs to install the OAA management chart and before proceeding from one stage to the next of the install. If this option is set the script will not prompt for missing information or between stages. If required information is missing it will exit in error instead.
   -u	No	Perform an update instead of an install. By default the script will determine whether to perform and install or an upgrade by looking for the helm chart previously installed.

   As the install progresses you will be prompted to answer various questions and perform certain tasks. The table below outlines some of the questions or tasks you may be asked to answer or perform:

   Output	Action
   Use 'podman login' to login into your private registry if you have not done so previously.Login successful? [Y/N]: Note: If using Docker the above will show docker login.	If your private Container Image Registry (CIR) where you store images requires a login, use podman login or docker login to log into the CIR and enter your credentials when prompted: podman login <container-registry.example.com> or: docker login <container-registry.example.com>
   Would you like to specify a kube context (otherwise 'kubernetes-admin@kubernetes' will be used)? [Y/N]:	If you have multiple kube contexts in your cluster you can choose which context to use. If you select "Y" you must type the context you wish to use. If you wish to use the default context chosen, or only have one context in your kube config, choose "N".

   Note:

   The table above does not include an exhaustive list of all the prompts you will see during the install as most are self explanatory.
   Once the Management Container installation is complete you will see output similar to the following:

   NAME: oaamgmt
   LAST DEPLOYED: <DATE>
   STATUS: deployed
   REVISION: 1
   TEST SUITE: None
   Waiting 15 secs for OAA mgmt deployment to start...
   Executing 'kubectl get pods oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv -n oaans'...
   NAME                                READY   STATUS              RESTARTS   AGE
   oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv   0/1     ContainerCreating   0          15s
   Waiting 15 secs for OAA mgmt deployment to run...
   Executing 'kubectl get pods oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv -n oaans'...
   NAME                                READY   STATUS              RESTARTS   AGE
   oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv   0/1     ContainerCreating   0          30s
   Waiting 15 secs for OAA mgmt deployment to run...
   Executing 'kubectl get pods oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv -n oaans'...
   NAME                                READY   STATUS              RESTARTS   AGE
   oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv   0/1     ContainerCreating   0          46s
   Waiting 15 secs for OAA mgmt deployment to run...
   Copying OAA properties file to oaans/oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv:/u01/oracle/scripts/settings
   Generating kube config for OAA mgmt pod 'oaans/oaamgmt-oaa-mgmt'.
   Using service account 'oaans/oaamgmt-oaa-mgmt'.
   Using token name 'oaamgmt-oaa-mgmt-token-5m88n'.
   Using cluster URL 'https://<URL>'.
   Cluster "oaa-cluster" set.
   User "oaa-service-account" set.
   Context "kubernetes-admin@kubernetes" created.
   Switched to context "kubernetes-admin@kubernetes".
   Copying OAA kube config files to oaans/oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv:/u01/oracle/scripts/creds...
   Using helm config '/home/opc/.config/helm/repositories.yaml'.
   Copying helm config to oaans/oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv:/u01/oracle/scripts/creds/helmconfig
   Copying certificates to oaans/oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv:/u01/oracle/scripts/creds
   Use command 'kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv -- /bin/bash' to get a shell to the OAA mgmt pod.
   From pod shell, use command 'kubectl get pods' to verify communication with the cluster.
   Continue OAA installation from the OAA mgmt pod.
   OAA management installation complete.

3. As per the output connect to the OAA management pod, for example:

   kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv9 -- /bin/bash

   This will take you into a bash shell inside the OAA management pod:

   [oracle@oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv /]$

Note:

If you encounter problems creating the Management Container, see Troubleshooting the Installation.

Next Steps: Deploying OAA, OARM, and OUA