Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCP test environment #484

Open
git-hyagi opened this issue Jul 12, 2022 · 4 comments
Open

OCP test environment #484

git-hyagi opened this issue Jul 12, 2022 · 4 comments
Labels

Comments

@git-hyagi
Copy link
Collaborator

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.

  • github runner resources 1
  • crc minimum system requirements 2
  • ocp minimum system requirements 3
@git-hyagi
Copy link
Collaborator Author

We can check https://docs.ci.openshift.org/docs/how-tos/testing-operator-sdk-operators/

@git-hyagi git-hyagi self-assigned this Jul 12, 2022
@git-hyagi
Copy link
Collaborator Author

We can also check microshift https://github.com/openshift/microshift#system-requirements

@stale
Copy link

stale bot commented Nov 15, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@stale stale bot added the stale label Nov 15, 2022
@git-hyagi git-hyagi removed their assignment Apr 11, 2023
@stale
Copy link

stale bot commented Apr 11, 2023

This issue is no longer marked for closure.

@stale stale bot removed the stale label Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant