apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "100129" uid: 66115c43-54a7-469c-b13f-55b5df47d08c spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T00:25:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.732µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 1.538147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 997.27µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:19:09Z" - latency: 1.450786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:18:09Z" - latency: 881.87µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:17:09Z" - latency: 1.287566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:16:09Z" - latency: 995.763µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:15:09Z" - latency: 1.220373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:14:09Z" - latency: 1.465587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:13:09Z" - latency: 1.421767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "102385" uid: 2d16d567-6cad-4213-9235-01d9f151abe6 spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:24:09Z" message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.39196ms message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:09Z" - latency: 7.297384ms message: 'load-balancer-api-external: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:24:09Z" - latency: 53.24944ms message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:23:09Z" - latency: 6.902933ms message: 'load-balancer-api-external: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:23:09Z" - latency: 54.103883ms message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:22:09Z" - latency: 8.450987ms message: 'load-balancer-api-external: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:22:09Z" - latency: 50.343923ms message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 8.580943ms message: 'load-balancer-api-external: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:21:09Z" - latency: 51.707021ms message: 'load-balancer-api-external: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 9.150449ms message: 'load-balancer-api-external: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:20:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "102386" uid: eeb2f89e-46f7-4cea-8dd8-2f9cb01de45b spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:24:09Z" message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.957936ms message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:09Z" - latency: 7.236266ms message: 'load-balancer-api-internal: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:24:09Z" - latency: 50.478605ms message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:23:09Z" - latency: 6.932784ms message: 'load-balancer-api-internal: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:23:09Z" - latency: 50.270409ms message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:22:09Z" - latency: 8.398167ms message: 'load-balancer-api-internal: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:22:09Z" - latency: 51.332561ms message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 8.601086ms message: 'load-balancer-api-internal: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:21:09Z" - latency: 63.617613ms message: 'load-balancer-api-internal: tcp connection to a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 9.097709ms message: 'load-balancer-api-internal: resolved host name a076d63db167a4a51863954deecefa98-6bdc7d033aceb6e1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T01:20:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-134-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "100127" uid: a83ea649-3664-4431-878c-e00b627db45c spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:25:09Z" message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.399218ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 2.287218ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 2.127687ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:19:09Z" - latency: 2.592488ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:18:09Z" - latency: 2.103737ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:17:09Z" - latency: 2.543205ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:16:09Z" - latency: 2.212577ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:15:09Z" - latency: 2.051045ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:14:09Z" - latency: 2.146364ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:13:09Z" - latency: 2.078501ms message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-137-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "100128" uid: e1ee99e3-3131-40a0-945c-72107eb27291 spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:25:09Z" message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.438967ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 2.006197ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 2.425823ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:19:09Z" - latency: 2.355717ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:18:09Z" - latency: 2.471952ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:17:09Z" - latency: 2.16183ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:16:09Z" - latency: 2.33739ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:15:09Z" - latency: 2.288368ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:14:09Z" - latency: 2.461915ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:13:09Z" - latency: 2.034501ms message: 'network-check-target-ip-10-0-137-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-140-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "100126" uid: 5cd3c2ba-809e-45e2-9666-245c281da755 spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:25:09Z" message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.993µs message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 806.144µs message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 1.060112ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:19:09Z" - latency: 1.359423ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:18:09Z" - latency: 1.25786ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:17:09Z" - latency: 1.48042ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:16:09Z" - latency: 947.73µs message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:15:09Z" - latency: 1.517636ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:14:09Z" - latency: 1.812825ms message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:13:09Z" - latency: 782.592µs message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:12:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:18:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-47.us-west-2.compute.internal uid: beea278b-6834-4e73-bd96-62ae9a14df2b resourceVersion: "102384" uid: 77f0bedc-bdb6-41e5-991f-dc6de2d6ad7c spec: sourcePod: network-check-source-6f78d59f99-9lx75 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T00:24:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:24:09Z" - latency: 1.96069ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:24:09Z" - latency: 918.044µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:23:09Z" - latency: 1.858184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:23:09Z" - latency: 953.979µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:22:09Z" - latency: 1.924304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:22:09Z" - latency: 1.196751ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:21:09Z" - latency: 1.81621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:21:09Z" - latency: 1.639267ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T01:20:09Z" - latency: 1.801323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T01:20:09Z" kind: List metadata: resourceVersion: ""