openshift / cluster-etcd-operator

Operator to manage the lifecycle of the etcd members of an OpenShift cluster
Apache License 2.0
96 stars 130 forks source link

WIP: initial test for kubelet fix on SNO #1188

Closed eggfoobar closed 9 months ago

eggfoobar commented 9 months ago

This PR is an attempt to validate another approach for resolving OCPBUGS-26489

Validating assumption that ignoring the NODE_IP for SNO deployments will allow cluster reboot to continue as normal

openshift-ci[bot] commented 9 months ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: eggfoobar Once this PR has been reviewed and has the lgtm label, please assign dusk125 for approval. For more information see the Kubernetes Code Review Process.

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

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

@eggfoobar: 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 7efbb5a2b759abafd1e237da26c84160602764ef link true /test unit
ci/prow/e2e-gcp-qe-no-capabilities 7efbb5a2b759abafd1e237da26c84160602764ef link true /test e2e-gcp-qe-no-capabilities

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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
eggfoobar commented 9 months ago

This won't work due to kube-api making use of downward api for host ip. This needs to be resolved another way, closing.