Platform, DevOps and Release Management (UXPROD-1814)

[UXPROD-3547] Rancher deployment pipeline NG Created: 08/Feb/22  Updated: 30/Nov/23  Resolved: 28/Jul/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Platform, DevOps and Release Management

Type: New Feature Priority: P3
Reporter: Vitaly Demchenko Assignee: Vitaly Demchenko
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-3387 Rancher Improvement: Implement Data M... Closed
Defines
is defined by RANCHER-169 Implement tenant creation via okapi Closed
is defined by RANCHER-170 [SPIKE] Investigate okapi kubernetes ... Draft
Relates
relates to RANCHER-76 Automate modules list compilation. Closed
relates to RANCHER-156 Analyze and adjust ansible roles usag... Closed
Epic Link: Platform, DevOps and Release Management
Development Team: Kitfox
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:

Now we have a bunch of various Jenkins jobs which create environments. All of the a copy-paste from one source with the same logic(for some moment in time). 

We need to create a single pipeline which is able to satisfy requirements for various environments - scratch, temporary, performance, karate, cypress.

In scope

Pipeline must provide next parameters:

  • Target cluster
  • Environment name
  • Tenant name to create
  • PostgreSQL database dump - [empty, available snapshots]- default empty
  • Number of replicas - default 1
  • Third-party components - self-managed, aws provided
  • Services versions - from database, from Platform-complete(specific branch) 

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions


Generated at Fri Feb 09 00:32:52 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.