openshift / cluster-kube-apiserver-operator

The kube-apiserver operator installs and maintains the kube-apiserver on a cluster
Apache License 2.0
74 stars 159 forks source link

OCPBUGS-35343: make shutdown-delay-duration configurable #1685

Open tkashem opened 6 months ago

openshift-ci-robot commented 6 months ago

@tkashem: This pull request references Jira Issue OCPBUGS-30860, which is valid.

3 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.17.0) matches configured target version for branch (4.17.0) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @geliu2016

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1685): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
tkashem commented 6 months ago

/cc @p0lyn0mial @vrutkovs

openshift-ci[bot] commented 6 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tkashem

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/cluster-kube-apiserver-operator/blob/master/OWNERS)~~ [tkashem] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
tkashem commented 6 months ago

/retest-required

openshift-ci[bot] commented 6 months ago

@tkashem: The following tests 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/unit 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link true /test unit
ci/prow/e2e-metal-single-node-live-iso 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link false /test e2e-metal-single-node-live-iso
ci/prow/k8s-e2e-gcp 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link true /test k8s-e2e-gcp
ci/prow/e2e-aws-operator-disruptive-single-node 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link false /test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-aws-ovn-single-node 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-operator-single-node 681dd36c2cc4aa5d8ce8bd008c4b2df557385cb7 link false /test e2e-gcp-operator-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
vrutkovs commented 5 months ago

/retitle OCPBUGS-35343: make shutdown-delay-duration configurable

openshift-ci-robot commented 5 months ago

@tkashem: This pull request references Jira Issue OCPBUGS-35343, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.17.0) matches configured target version for branch (4.17.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1685): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.