Advanced Cluster Security Demo

Setup Instructions

Below are the instrcutions to set up the demo.

There is a single installation script called install-all-setup.sh. It runs basic-setup first, then runs five other setup scripts in parallel:

  • FAM (file activity monitoring)

  • Persus monitoring in the console

  • MCP server setup

  • OpenShift Pipelines (Tekton) RHACS tasks

  • Policy as Code (GitOps) via Argo CD

The lab environment includes a sample virtual machine for vulnerability-management demos; you do not need to provision or register a VM as part of this install.

Requirements

All requirements are configured by the basic-setup script and the parallel setup steps above.

Set up scripts

Procedure

  1. Copy and paste the following command into your terminal:

    source ~/.bashrc
git clone https://github.com/mfosterrox/rhacs-demo.git || (cd rhacs-demo && git pull)
cd rhacs-demo
chmod +x install-all-setup.sh verify-all-setup.sh
./install-all-setup.sh -p {acs_portal_password}

  2. Wait until the script finishes. You should see Phase 1 (basic-setup) complete, then Phase 2 parallel jobs start and Waiting for N parallel job(s) complete without errors.

If a script fails, you can run the indivdual script again. The error messages will provide the command to rerun the script.

Verify success

Run the verification script.

cd ~/rhacs-demo
source ~/.bashrc
./verify-all-setup.sh

OUTPUT:

[STEP] Summary
  ✓ No failed checks (0 warning(s))

Accessing the Consoles

With a proper installation, you should be able to access the following consoles:

  • OpenShift Console

  • RHACS Console

OpenShift Console

Access the consoles in other tabs for demonstration purposes.

Access the OpenShift Console from the OpenShift Console tab in the right panel, or open it directly: {openshift_cluster_console_url}[window=blank]

Username:

{openshift_cluster_admin_username}

Password:

{openshift_cluster_admin_password}

RHACS Console

Access the RHACS Console from the RHACS Console tab in the right panel, or open it directly: {acs_route}[window=blank]

Choose the standard username and password option, and NOT the monitoring login path.

Username:

{acs_portal_username}

Password:

{acs_portal_password}

Bastion Host

If you need to access the bastion host, for diagnostics or troubleshooting, use the following SSH command:

ssh {bastion_ssh_user_name}@{bastion_public_hostname} -p {bastion_ssh_port}

When prompted for a password, use:

{bastion_ssh_password}