How to recreate Eureka Rancher environment
How to recreate Eureka Rancher environment with default parameters
Purpose
If you need to delete and recreate your Eureka Rancher environment, use this aggregated pipeline. It's useful for refreshing an environment with the latest configurations or recovering from issues.
Target pipeline: recreateTeamNamespace
What the Pipeline Does
This pipeline performs two sequential operations:
Delete existing environment - Removes the current namespace and all its resources
Create new environment - Provisions a fresh environment with the same name, links, and configurations
Parameters
Parameter | Required/Optional | Description | Default/Value |
|---|---|---|---|
PLATFORM | Required | Platform type - Must be set to EUREKA | EUREKA |
CLUSTER | Required | Select target cluster (e.g., | |
NAMESPACE | Required | Your team's namespace name (e.g., | |
CONFIG_TYPE | Required | Deployment configuration: • development - for Dev clusters • testing - for Testing clusters • performance - for Perf clusters | development |
SC_NATIVE | Optional | Use native sidecar image (set false for Java-based SC) | true |
CONSORTIA_EXTRA | Optional | Include 2nd consortium setup | false |
Pre-configured Environment Settings
The pipeline creates environments with the following fixed configurations (not configurable via parameters):
Core Configuration
FOLIO Branch:
snapshotOkapi Version:
latestApplication Set:
CompleteUI Build: Enabled
Sanity Check: Enabled (runs automatically after creation)
Feature Flags
LOAD_REFERENCE: ✓ Enabled
LOAD_SAMPLE: ✓ Enabled
CONSORTIA: ✓ Enabled
LINKED_DATA: ✓ Enabled
SPLIT_FILES: ✓ Enabled
HAS_SECURE_TENANT: ✓ Enabled (on University tenant)
RW_SPLIT: ✗ Disabled
GREENMAIL: ✗ Disabled
MOCK_SERVER: ✗ Disabled
RTR: ✗ Disabled
ECS_CCL: ✗ Disabled
DATASET: ✗ Disabled
Infrastructure
PostgreSQL: Built-in (version 16.8)
Kafka: Built-in
OpenSearch: AWS
S3: Built-in (Minio)
Steps to Perform
Navigate to the recreateTeamNamespace job
Click Build with Parameters
Fill in the required parameters:
Set PLATFORM to
EUREKASelect your CLUSTER (e.g.,
folio-edev)Enter your NAMESPACE name
Set CONFIG_TYPE (typically
development)Optionally adjust SC_NATIVE and CONSORTIA_EXTRA
Click Build button
Wait for completion (~1 hour)
Important Notes
Automated Scheduling: The pipeline runs automatically every day at 8 PM UTC for the
eurekanamespace infolio-edevclusterConcurrent Builds: Disabled to prevent conflicts - only one recreation can run at a time
Secure Tenant: Automatically configured on the University consortium tenant
Sanity Check: Cypress tests run automatically after environment creation to verify the setup
Build Retention: Last 30 builds are kept
Triggered Jobs
This pipeline orchestrates two other jobs:
deleteNamespace - Removes the existing namespace
createNamespaceFromBranch - Creates the new namespace with all configurations
Both jobs run sequentially and must complete successfully for the recreation to succeed.
Expected Duration
Total Time: Approximately 1 hour
Delete phase: ~5-10 minutes
Create phase: ~45-50 minutes
Sanity check: ~5-10 minutes
Troubleshooting
If the job fails during deletion, verify the namespace exists and you have permissions
If the job fails during creation, check the logs of the
createNamespaceFromBranchsub-jobIf sanity checks fail, the environment is created but may have issues - review Cypress test results
For scheduled runs, the job only recreates the
eurekanamespace infolio-edevcluster
Example Configuration
Standard team environment recreation:
PLATFORM:
EUREKACLUSTER:
folio-edevNAMESPACE:
folijetCONFIG_TYPE:
developmentSC_NATIVE:
trueCONSORTIA_EXTRA:
false