Skip to content

Comments

First attempt to the ACS onboarding#100

Draft
p-rog wants to merge 10 commits intovalidatedpatterns:mainfrom
p-rog:acs-onboarding
Draft

First attempt to the ACS onboarding#100
p-rog wants to merge 10 commits intovalidatedpatterns:mainfrom
p-rog:acs-onboarding

Conversation

@p-rog
Copy link

@p-rog p-rog commented Feb 23, 2026

Red Hat Advanced Cluster Security (RHACS/StackRox) consists of two main deployment types:

Central Services (Hub Cluster)

Central:

  • Management console and API server
  • Policy engine and enforcement
  • Centralized data aggregation
  • Vulnerability database management

Scanner:

  • Vulnerability scanning for container images
  • Pulls image layers from registries
  • Identifies installed packages
  • Compares against CVE databases

Secured Cluster Services (Per Cluster)

Sensor:

  • Monitors cluster activity
  • Listens to Kubernetes API events
  • Collects data from Collectors
  • Reports cluster state to Central

Admission Controller:

  • Policy enforcement at deployment time
  • Validates resources before admission
  • Prevents policy violations
  • Configurable bypass options

Collector:

  • Per-node DaemonSet deployment
  • Runtime monitoring and network activity
  • Container activity analysis
  • Sends data to Sensor

@p-rog p-rog marked this pull request as draft February 23, 2026 16:27
@p-rog
Copy link
Author

p-rog commented Feb 23, 2026

I have to fix the ACS init secret issue:

  1. Init bundle can ONLY be generated AFTER ACS Central is deployed and running
  2. The Validated Patterns framework processes ALL secrets BEFORE deploying applications
  3. With onMissingValue: error, installation fails if the secret doesn't exist in Vault

Przemyslaw Roguski and others added 2 commits February 23, 2026 20:17
- Fix indentation in values-hub.yaml (stackrox namespace)
- Comment out acs-init-bundle secret (not needed for same-cluster deployment)
- RHACS operator auto-generates auth for co-located Central + SecuredCluster

Fixes vault namespace deployment issue.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@p-rog
Copy link
Author

p-rog commented Feb 23, 2026

The secret issue is fixed.
I'm working on Vault service creation issue.

Przemyslaw Roguski and others added 7 commits February 24, 2026 13:34
This commit resolves two critical issues preventing ACS Central and
SecuredCluster Custom Resources from being deployed:

1. Uncommented extraValueFiles for acs-central and acs-secured-cluster
   applications in values-hub.yaml. This enables helm charts to receive
   global configuration values (localClusterDomain, secretStore, etc.)
   required for proper template rendering.

2. Added ExternalSecret template for central-htpasswd admin password.
   This syncs the admin password from Vault (hub/infra/acs) to the
   Kubernetes secret expected by the Central CR.

With these fixes, ArgoCD will successfully render and deploy:
- Central CR (Wave 10) with PostgreSQL DB and Scanner components
- Init bundle job (Wave 12) to generate TLS secrets
- OAuth integration job (Wave 13) for OpenShift authentication
- SecuredCluster CR (Wave 15) with Sensor, Collector, and Admission Controller

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
… the central-cr.yaml and secured-cluster-cr.yaml, removing the perNode duplication, adding explicit scannerV4 configuration to central-cr.yaml
The cluster only has ACM release-2.15 channel available.
Changed from release-2.14 to release-2.15 to fix subscription failure.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant