OCP test environment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
It would be good to add a job to test pulp-operator deployment in OCP environments.
Describe the solution you'd like
The tests that we are doing are not covering some OCP specific configurations/resources, for example, the pulp-route role and the imagePullSecret added by OCM.
This new test environment will also be very helpful to check and test the possible breaking change of PSP on k8s 1.25, allowing to test the usage of the new (OCP only) restricted-v2 SCC.
Describe alternatives you've considered
We could check if we can run CRC or OCP on a single node.
Additional context
We will probably have some resource constraints to run the environment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing the existing CI jobs and deployment-test entry points, then assess CRC or single-node OCP against GitHub runner and environment resource constraints. Done means an automated job exercises pulp-operator deployment in OCP and covers OCP-specific resources such as pulp-route, imagePullSecret, and restricted-v2 SCC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100