bcgov / bcgov/wps

Put stateful sets in its own openshift template

Open
#2,217 0 comments 0 reactions 0 assignees View on GitHub
4Refinement Task
Dominant language
Python
Stars
65
Forks
11
Avg merge
1d 2h
Merged PRs (30d)
70

Description

**Describe the task**
We have ".bc.yml", ".dc.yml", ".config.yml" and ".cronjob.yml" - wonder if we need a similar convention for stateful sets?
**Acceptance Criteria**
- [ ] Stateful sets live in their own template

**Additional context**
- For consistency

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing .bc.yml, .dc.yml, .config.yml, and .cronjob.yml templates and identify where StatefulSet definitions currently live. Compare their conventions and determine the template boundary needed for StatefulSets. Done means StatefulSets reside in their own template and the deployment configuration still references them correctly.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.