apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23660" uid: 55a01145-19ea-4851-a098-603f1ddefae4 spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T12:46:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 1.184959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 1.279694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 1.16013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 1.396956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 774.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:20Z" - latency: 1.24526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:20Z" - latency: 1.310939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:20Z" - latency: 1.240178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:20Z" - latency: 1.172366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23661" uid: a6cf90b6-7fea-4100-a0f4-640368f1698d spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:45:20Z" message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.567975ms message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 8.589678ms message: 'load-balancer-api-external: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:21:20Z" - latency: 54.715184ms message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 8.765764ms message: 'load-balancer-api-external: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:20:20Z" - latency: 55.900186ms message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 7.866169ms message: 'load-balancer-api-external: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:19:20Z" - latency: 55.551396ms message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 9.162813ms message: 'load-balancer-api-external: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:18:20Z" - latency: 54.652336ms message: 'load-balancer-api-external: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 7.900013ms message: 'load-balancer-api-external: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23662" uid: 5aa9f720-fdf3-462f-a8ce-06323ce7dc41 spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T12:45:20Z" message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.595185ms message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 8.541953ms message: 'load-balancer-api-internal: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:21:20Z" - latency: 58.735546ms message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 8.645475ms message: 'load-balancer-api-internal: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:20:20Z" - latency: 54.378973ms message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 7.960393ms message: 'load-balancer-api-internal: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:19:20Z" - latency: 58.28649ms message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 9.31587ms message: 'load-balancer-api-internal: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:18:20Z" - latency: 54.697534ms message: 'load-balancer-api-internal: tcp connection to ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 7.878317ms message: 'load-balancer-api-internal: resolved host name ad8c65040d3954e90b2449d79a0709a3-48f5ae5b3a5c707c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-131-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23656" uid: c7c1d392-2418-45af-a7b7-37860b6ada1c spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:46:20Z" message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.18µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 1.453532ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 873.129µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 1.917542ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 1.455842ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 734.239µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:20Z" - latency: 850.054µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:20Z" - latency: 1.575908ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:20Z" - latency: 1.365567ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:20Z" - latency: 904.416µs message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-138-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23657" uid: e74f76c0-1e6a-4fee-b133-ca593f7c8be9 spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:46:20Z" message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.001556ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 2.298942ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 1.945446ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 3.295906ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 1.710767ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 1.646392ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:20Z" - latency: 1.893328ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:20Z" - latency: 2.444085ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:20Z" - latency: 2.036003ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:20Z" - latency: 2.054003ms message: 'network-check-target-ip-10-0-138-206: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-ip-10-0-141-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23658" uid: da216283-c199-4b83-822e-cea5d587240d spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T12:46:20Z" message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212966ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 2.117349ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 2.382037ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 2.027777ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 2.191077ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 1.948174ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:16:20Z" - latency: 2.185091ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:15:20Z" - latency: 1.905486ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:14:20Z" - latency: 2.336253ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:13:20Z" - latency: 2.132431ms message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:12:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T12:39:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-203.us-west-1.compute.internal uid: 93388094-ae1b-41a6-ad4c-fdc1b59551ec resourceVersion: "23659" uid: bce4d93f-ad35-45e4-b0f6-ee55568ace02 spec: sourcePod: network-check-source-6f78d59f99-fhcsj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T12:45:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.322198ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:21:20Z" - latency: 1.862669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:21:20Z" - latency: 1.004659ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:20:20Z" - latency: 1.829156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:20:20Z" - latency: 889.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:19:20Z" - latency: 1.887271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:19:20Z" - latency: 1.408425ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:18:20Z" - latency: 2.267454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:18:20Z" - latency: 719.756µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T13:17:20Z" - latency: 1.910403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T13:17:20Z" kind: List metadata: resourceVersion: ""