-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
3
-
False
-
-
False
-
-
-
Integration & Delivery - 263
-
0
-
0.000
We have several projects in Fedora's OpenShift that we rely on:
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-ci.yml
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-cincinnati.yml
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-koji-tagger.yml
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-ostree-importer.yml
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/fedora-coreos-pipeline.yml
- https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/fedora-ostree-pruner.yml
Most of them (if not all) are using outdated/deprecated constructs like `DeploymentConfig`. `BuildConfig` may be deprecated too. In all cases we need to update our projects to use new APIs/Objects so that they don't cease to work in the future.