apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235441" uid: 20d7a60c-4327-45ee-b334-09362ff84848 spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T17:41:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:21Z" - latency: 1.600377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:21Z" - latency: 1.910635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:21Z" - latency: 1.064267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:21Z" - latency: 1.269992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:21Z" - latency: 1.354906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:53:21Z" - latency: 1.490093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:52:21Z" - latency: 1.456307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:51:21Z" - latency: 1.231841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:50:21Z" - latency: 1.283534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235442" uid: eab15e6e-a3e2-4207-b09b-c5c1b1154e95 spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:40:21Z" message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.341654ms message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:21Z" - latency: 7.150423ms message: 'load-balancer-api-external: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:58:21Z" - latency: 4.71336ms message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:21Z" - latency: 6.40512ms message: 'load-balancer-api-external: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:57:21Z" - latency: 4.79911ms message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:21Z" - latency: 6.657525ms message: 'load-balancer-api-external: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:56:21Z" - latency: 5.210655ms message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:21Z" - latency: 6.620855ms message: 'load-balancer-api-external: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:55:21Z" - latency: 5.228964ms message: 'load-balancer-api-external: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:21Z" - latency: 6.906939ms message: 'load-balancer-api-external: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:54:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235443" uid: c6d3b0ab-5204-433f-893e-87bf2612f2ba spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:40:21Z" message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.487133ms message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:21Z" - latency: 7.184444ms message: 'load-balancer-api-internal: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:58:21Z" - latency: 4.729911ms message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:21Z" - latency: 6.363192ms message: 'load-balancer-api-internal: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:57:21Z" - latency: 4.817831ms message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:21Z" - latency: 6.638988ms message: 'load-balancer-api-internal: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:56:21Z" - latency: 5.219122ms message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:21Z" - latency: 6.646359ms message: 'load-balancer-api-internal: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:55:21Z" - latency: 5.208265ms message: 'load-balancer-api-internal: tcp connection to a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:21Z" - latency: 6.938416ms message: 'load-balancer-api-internal: resolved host name a6b7c74f468274e48ae2f50a27f493f6-18198e57765c773b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:54:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-network-check-target-ip-10-0-135-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235439" uid: 57513141-c0e6-49b9-a3ce-709df2517547 spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:41:21Z" message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.363144ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:21Z" - latency: 979.54µs message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:21Z" - latency: 1.666248ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:21Z" - latency: 1.371479ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:21Z" - latency: 1.192597ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:21Z" - latency: 987.343µs message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:53:21Z" - latency: 1.781072ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:52:21Z" - latency: 1.210044ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:51:21Z" - latency: 1.462009ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:50:21Z" - latency: 1.537137ms message: 'network-check-target-ip-10-0-135-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:49:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-network-check-target-ip-10-0-141-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235519" uid: c22493d9-27e4-49af-a175-e547afdeeacb spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:41:30Z" message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.231549ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:30Z" - latency: 2.039765ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:30Z" - latency: 973.306µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:30Z" - latency: 2.422094ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:30Z" - latency: 1.123294ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:30Z" - latency: 3.300151ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:53:30Z" - latency: 2.359311ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:52:30Z" - latency: 2.373658ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:51:30Z" - latency: 2.0381ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:50:30Z" - latency: 3.219723ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:49:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-network-check-target-ip-10-0-142-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235484" uid: 8fe433e9-85fc-4df6-ba6a-b12a869c0d06 spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:41:26Z" message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181026ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:26Z" - latency: 2.585898ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:26Z" - latency: 2.775278ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:26Z" - latency: 1.598184ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:26Z" - latency: 6.495531ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:26Z" - latency: 1.202015ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:53:26Z" - latency: 2.633024ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:52:26Z" - latency: 1.383379ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:51:26Z" - latency: 831.551µs message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:50:26Z" - latency: 1.107987ms message: 'network-check-target-ip-10-0-142-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:49:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:34:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-5-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-5.us-east-2.compute.internal uid: 65548c09-f241-43ac-8974-a1593a2edf46 resourceVersion: "235440" uid: 34634c9e-5b3a-4d63-af36-4d8757bedd52 spec: sourcePod: network-check-source-6f78d59f99-bbsgc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T17:40:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.42153ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:58:21Z" - latency: 2.184231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:58:21Z" - latency: 804.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:57:21Z" - latency: 1.976249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:57:21Z" - latency: 2.277233ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:56:21Z" - latency: 1.982133ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:56:21Z" - latency: 2.315862ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:55:21Z" - latency: 2.024432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:55:21Z" - latency: 2.276299ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:54:21Z" - latency: 2.044041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:54:21Z" kind: List metadata: resourceVersion: ""