openshift / openshift/oadp-operator
4.14 jobs DeploymentConfig warnings
Open
Nobody has claimed this yet.
CI
lifecycle/frozen
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
4.14 jobs (example) are warning about deprecation of DeploymentConfig. The warning can be seen during the execution of dc-post-restore.sh script:
2024/01/08 05:52:49 command: /usr/bin/bash /go/src/github.com/openshift/oadp-operator/docs/scripts/dc-post-restore.sh mongo-blockdevice-e2e-6f7ca013-ade9-11ee-9323-0a580a80e67c
2024/01/08 05:52:49 stdout:
restore: mongo-blockdevice-e2e-6f7ca013-ade9-11ee-9323-0a580a80e67c
label: mongo-blockdevice-e2e-6f7ca013-ade9-11ee-9323-0a580a80e67c
Deleting disconnected restore pods
No resources found
2024/01/08 05:52:49 stderr:
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavailable in v4.10000+
2024/01/08 05:52:49 err: <nil>
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
Inspect docs/scripts/dc-post-restore.sh and the linked 4.14 job log. Trace the command that triggers the DeploymentConfig deprecation warning, then verify that the 4.14 job completes without that warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100