apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "29575" uid: 17a56b56-b06c-4919-8da5-5627186efc19 spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:35:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 1.59198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:15Z" - latency: 1.112507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:15Z" - latency: 1.219085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:15Z" - latency: 1.678371ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:15Z" - latency: 1.361987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:15Z" - latency: 896.391µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:15Z" - latency: 1.460894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:15Z" - latency: 1.241557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:15Z" - latency: 1.177205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:33:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "34041" uid: 7b371e25-ee85-4a58-a3d4-ccf8b852564d spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:34:15Z" message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.907412ms message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:15Z" - latency: 7.103128ms message: 'load-balancer-api-external: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:46:15Z" - latency: 4.618166ms message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:15Z" - latency: 10.810315ms message: 'load-balancer-api-external: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:45:15Z" - latency: 10.502455ms message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:15Z" - latency: 6.424897ms message: 'load-balancer-api-external: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:15Z" - latency: 5.790796ms message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:15Z" - latency: 7.07211ms message: 'load-balancer-api-external: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:15Z" - latency: 4.586609ms message: 'load-balancer-api-external: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 7.478133ms message: 'load-balancer-api-external: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "34042" uid: 30415c07-3a25-48c2-9d01-b989f08bfa47 spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:34:15Z" message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.830677ms message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:15Z" - latency: 7.137709ms message: 'load-balancer-api-internal: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:46:15Z" - latency: 3.332743061s message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:15Z" - latency: 10.779962ms message: 'load-balancer-api-internal: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:45:15Z" - latency: 27.417977ms message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:15Z" - latency: 6.343793ms message: 'load-balancer-api-internal: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:15Z" - latency: 4.994242ms message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:15Z" - latency: 7.101846ms message: 'load-balancer-api-internal: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:15Z" - latency: 3.584018ms message: 'load-balancer-api-internal: tcp connection to a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 7.529484ms message: 'load-balancer-api-internal: resolved host name a425b7f6eb33c4de28708ac8436e3c1d-7d2bba31d28fadf9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-network-check-target-ip-10-0-130-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "29574" uid: 952b10d4-ebb2-4a8d-8896-b4be547ae92e spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:15Z" message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.472426ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 2.356554ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:15Z" - latency: 2.164364ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:15Z" - latency: 2.285749ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:15Z" - latency: 2.499711ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:15Z" - latency: 2.319034ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:15Z" - latency: 2.458385ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:15Z" - latency: 2.114035ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:15Z" - latency: 2.296593ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:15Z" - latency: 2.434393ms message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:33:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-network-check-target-ip-10-0-134-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "29572" uid: 1c6b70b2-9869-4535-96cd-b5b3527873ca spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:15Z" message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088509ms message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 918.576µs message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:15Z" - latency: 913.784µs message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:15Z" - latency: 1.583228ms message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:15Z" - latency: 1.423202ms message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:15Z" - latency: 974.08µs message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:15Z" - latency: 959.692µs message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:15Z" - latency: 904.716µs message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:15Z" - latency: 1.069723ms message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:15Z" - latency: 1.24417ms message: 'network-check-target-ip-10-0-134-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:33:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-network-check-target-ip-10-0-136-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "29573" uid: f7df3dd1-81bc-4713-88ff-90477dccfe6d spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:35:15Z" message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.031594ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 1.927298ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:41:15Z" - latency: 2.032273ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:40:15Z" - latency: 1.995729ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:39:15Z" - latency: 2.006818ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:38:15Z" - latency: 2.172091ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:37:15Z" - latency: 1.894182ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:36:15Z" - latency: 2.01626ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:35:15Z" - latency: 2.047175ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:34:15Z" - latency: 1.945858ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:33:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:28:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-98-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-98.ec2.internal uid: 8c4542e2-111d-4548-bb46-06a8dfca76d7 resourceVersion: "34040" uid: 6a32e9f3-9576-4087-94ee-b176656aca19 spec: sourcePod: network-check-source-989f8b8dc-t7llq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:34:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.065646ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:46:15Z" - latency: 2.113737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:46:15Z" - latency: 936.636µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:45:15Z" - latency: 1.995489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:45:15Z" - latency: 1.087962ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:44:15Z" - latency: 1.64903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:44:15Z" - latency: 853.932µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:43:15Z" - latency: 1.772299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:43:15Z" - latency: 1.094546ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:42:15Z" - latency: 1.660758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:42:15Z" kind: List metadata: resourceVersion: ""