$ helm repo update- Documentation
- Red Hat Advanced Cluster Security for Kubernetes
- RHACS Cloud Service
- Upgrading RHACS Cloud Service
- Upgrading secured clusters in RHACS Cloud Service by using Helm charts history bug_report picture_as_pdf
OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
- About
- Release notes
- RHACS Cloud Service
- Service description
- Overview of responsibilities for RHACS Cloud Service
- RHACS Cloud Service architecture
- Getting started with RHACS Cloud Service
- Default resource requirements for RHACS Cloud Service
- Recommended resource requirements for RHACS Cloud Service
- Setting up RHACS Cloud Service with Red Hat OpenShift secured clusters
- Creating a RHACS Cloud Service instance on Red Hat Cloud
- Creating a project on your Red Hat OpenShift secured cluster
- Generating an init bundle for secured clusters
- Applying an init bundle for secured clusters
- Installing the RHACS Operator for RHACS Cloud Service
- Installing secured cluster services from RHACS Cloud Service
- Configuring the proxy for secured cluster services in RHACS Cloud Service
- Verifying installation of secured clusters
- Setting up RHACS Cloud Service with Kubernetes secured clusters
- Creating a RHACS Cloud Service instance for Kubernetes clusters
- Generating an init bundle for Kubernetes secured clusters
- Applying an init bundle for Kubernetes secured clusters
- Installing secured cluster services from RHACS Cloud Service on Kubernetes clusters
- Verifying installation of secured clusters
- Upgrading RHACS Cloud Service
- Architecture
- Installing
- High-level RHACS installation overview
- Default resource requirements for RHACS
- Recommended resource requirements for RHACS
- Installing RHACS on Red Hat OpenShift
- Installing Central services for RHACS on Red Hat OpenShift
- Configuring Central configuration options for RHACS using the Operator
- Generating and applying an init bundle for RHACS on Red Hat OpenShift
- Installing Secured Cluster services for RHACS on Red Hat OpenShift
- Configuring Secured Cluster services options for RHACS using the Operator
- Verifying installation of RHACS on Red Hat OpenShift
- Installing RHACS on other platforms
- Uninstalling Red Hat Advanced Cluster Security for Kubernetes
- Configuring
- Adding custom certificates
- Adding trusted certificate authorities
- Reissuing internal certificates
- Adding security notices
- Enabling offline mode
- Enabling alert data retention
- Exposing the RHACS portal over HTTP
- Configuring automatic upgrades for secured clusters
- Configuring automatic removal of nonactive clusters
- Configuring a proxy for external network access
- Generating a diagnostic bundle
- Configuring endpoints
- Monitoring
- Enabling audit logging
- Configuring API tokens
- Using declarative configuration
- Inviting users to your RHACS instance
- Operating
- Viewing the dashboard
- Using Compliance Operator with RHACS
- Managing compliance
- Evaluating security risks
- Using admission controller enforcement
- Managing security policies
- Default security policies
- Managing network policies
- Build-time network policy tools
- Auditing listening endpoints
- Reviewing cluster configuration
- Examining images for vulnerabilities
- Verifying image signatures
- Managing vulnerabilities
- Responding to violations
- Using deployment collections
- Searching and filtering
- Managing user access
- Using the system health dashboard
- Using the administration events page
- Integrating
- Integrating with image registries
- Integrating with CI systems
- Integrating with PagerDuty
- Integrating with Slack
- Integrating by using generic webhooks
- Integrating with QRadar
- Integrating with ServiceNow
- Integrating with Sumo Logic
- Integrating with Google Cloud Storage
- Integrating by using the syslog protocol
- Integrating with Amazon S3
- Integrating with Google Cloud Security Command Center
- Integrating with Splunk
- Integrating with image vulnerability scanners
- Integrating with Jira
- Integrating with email
- Integrating with cloud management platforms
- Integrating using short-lived tokens
- Backup and restore
- Upgrading
- roxctl CLI
- Troubleshooting Collector
- Troubleshooting Central
- Telemetry
- Support
- API reference
- AdministrationEventService
- AdministrationUsageService
- AlertService
- APITokenService
- AuthProviderService
- AuthService
- CentralHealthService
- CloudSourcesService
- ClusterCVEService
- ClusterInitService
- ClustersService
- CollectionService
- ComplianceManagementService
- ComplianceService
- ConfigService
- CredentialExpiryService
- DBService
- DebugService
- DeclarativeConfigHealthService
- DelegatedRegistryConfigService
- DeploymentService
- DetectionService
- DiscoveredClustersService
- ExternalBackupService
- FeatureFlagService
- GroupService
- GRPCPreferencesService
- ImageCVEService
- ImageIntegrationService
- ImageService
- IntegrationHealthService
- ListeningEndpointsService
- MetadataService
- MitreAttackService
- NamespaceService
- NetworkBaselineService
- NetworkGraphService
- NetworkPolicyService
- GetAllowedPeersFromCurrentPolicyForDeployment
- ApplyNetworkPolicy
- ApplyNetworkPolicyYamlForDeployment
- GetDiffFlowsBetweenPolicyAndBaselineForDeployment
- GetNetworkGraph
- GetBaselineGeneratedNetworkPolicyForDeployment
- GenerateNetworkPolicies
- GetNetworkPolicies
- GetNetworkGraphEpoch
- GetNetworkPolicy
- SendNetworkPolicyYAML
- SimulateNetworkGraph
- GetDiffFlowsFromUndoModificationForDeployment
- GetUndoModification
- GetUndoModificationForDeployment
- NodeCVEService
- NodeService
- NotifierService
- PingService
- PodService
- PolicyCategoryService
- PolicyService
- ProbeUploadService
- ProcessBaselineService
- ProcessService
- RbacService
- ReportConfigurationService
- ReportService
- RoleService
- ComputeEffectiveAccessScope
- GetMyPermissions
- ListPermissionSets
- DeletePermissionSet
- GetPermissionSet
- PutPermissionSet
- PostPermissionSet
- GetResources
- GetRoles
- DeleteRole
- GetRole
- CreateRole
- UpdateRole
- GetNamespacesForClusterAndPermissions
- GetClustersForPermissions
- ListSimpleAccessScopes
- DeleteSimpleAccessScope
- GetSimpleAccessScope
- PutSimpleAccessScope
- PostSimpleAccessScope
- SearchService
- SecretService
- SensorUpgradeService
- ServiceAccountService
- ServiceIdentityService
- SignatureIntegrationService
- SummaryService
- TelemetryService
- UserService
- VulnerabilityRequestService
- VulnMgmtService
×
Upgrading secured clusters in RHACS Cloud Service by using Helm charts
You can upgrade your secured clusters in RHACS Cloud Service by using Helm charts.
If you installed RHACS secured clusters by using Helm charts, you can upgrade to the latest version of RHACS by updating the Helm chart and running the helm upgrade command.
Updating the Helm chart repository
You must always update Helm charts before upgrading to a new version of Red Hat Advanced Cluster Security for Kubernetes.
Prerequisites
-
You must have already added the Red Hat Advanced Cluster Security for Kubernetes Helm chart repository.
-
You must be using Helm version 3.8.3 or newer.
Procedure
-
Update Red Hat Advanced Cluster Security for Kubernetes charts repository.
Verification
-
Run the following command to verify the added chart repository:
$ helm search repo -l rhacs/
Running the Helm upgrade command
You can use the helm upgrade command to update Red Hat Advanced Cluster Security for Kubernetes (RHACS).
Prerequisites
-
You must have access to the
values-private.yamlconfiguration file that you have used to install Red Hat Advanced Cluster Security for Kubernetes (RHACS). Otherwise, you must generate thevalues-private.yamlconfiguration file containing root certificates before proceeding with these commands.
Procedure
-
Run the helm upgrade command and specify the configuration files by using the
-foption:$ helm upgrade -n stackrox stackrox-secured-cluster-services \ rhacs/secured-cluster-services --version <current-rhacs-version> \(1) -f values-private.yaml1 Use the -f option to specify the paths for your YAML configuration files.