Open slashpai opened 1 month ago
@slashpai: This pull request references MON-3971 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
Hello @slashpai! Some important instructions when contributing to openshift/api: API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.
/retest
/retest
/payload 4.17 nightly blocking
@slashpai: trigger 9 job(s) of type blocking for the nightly release of OCP 4.17
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/35832820-554f-11ef-9dcc-9fa7f4650624-0
Thanks!
Maybe we should also clean it in payload-command/render/renderassets/rendered_manifests_test.go?
/hold Let's wait for https://github.com/openshift/api/pull/1780 to set the pace as there are still discussions around "featuregates removing" https://github.com/openshift/api/pull/1780#issuecomment-1993986689
FYI https://github.com/openshift/api/pull/1780 was merged. Reading the latest discussions, I think we should wait until version 4.19 to merge this one.
Looking at the slack thread, I think we are ok to move forward, can you rebase please to address conflicts
@slashpai: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-azure | 49ba8ebd11182d837fb2b3beb08bd2f6973a180b | link | false | /test e2e-azure |
Full PR test history. Your PR dashboard.
Feature was promoted to GA 4 months ago in 4.17
/lgtm
PR needs rebase.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: JoelSpeed, slashpai
The full list of commands accepted by this bot can be found here.
The pull request process is described here
cluster-monitoring-operator now by default installs and configures metrics-server and it doesn't need to be behind feature gate anymore.