apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "69972" uid: 9f01cc9d-8605-442d-93e8-5ca8e28856c6 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T14:34:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:16:57Z" - latency: 846.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 1.014019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 810.236µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 1.260972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 1.084502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 1.121096ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:10:57Z" - latency: 1.047655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:09:57Z" - latency: 939.637µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:08:57Z" - latency: 1.379719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "68797" uid: e8d5d48a-846b-4c9a-80d1-dcb7f965e46e spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T14:33:57Z" message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.155637ms message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 7.712676ms message: 'load-balancer-api-external: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:15:57Z" - latency: 4.075628ms message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 6.742849ms message: 'load-balancer-api-external: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:14:57Z" - latency: 4.672236ms message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 6.942282ms message: 'load-balancer-api-external: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:13:57Z" - latency: 5.119621ms message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 7.075195ms message: 'load-balancer-api-external: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:12:57Z" - latency: 4.159128ms message: 'load-balancer-api-external: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 6.580998ms message: 'load-balancer-api-external: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "68796" uid: e0c9609b-645e-44b9-af46-59ee5a6c43f9 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T14:33:57Z" message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.238118ms message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 7.651144ms message: 'load-balancer-api-internal: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:15:57Z" - latency: 4.00949ms message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 6.699514ms message: 'load-balancer-api-internal: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:14:57Z" - latency: 4.709745ms message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 7.040014ms message: 'load-balancer-api-internal: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:13:57Z" - latency: 5.132127ms message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 7.354568ms message: 'load-balancer-api-internal: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:12:57Z" - latency: 4.337659ms message: 'load-balancer-api-internal: tcp connection to a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 6.473205ms message: 'load-balancer-api-internal: resolved host name a3897bcffab5549feb12b82c64834111-c0af552b7cc587c9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T15:11:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-network-check-target-ip-10-0-131-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "69969" uid: 6504525d-757f-4fda-82c2-396148aa5906 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T14:34:57Z" message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.054356ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:16:57Z" - latency: 2.364375ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 1.772883ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 2.086179ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 2.375822ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 2.006854ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 2.32142ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:10:57Z" - latency: 2.128763ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:09:57Z" - latency: 2.265788ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:08:57Z" - latency: 2.40378ms message: 'network-check-target-ip-10-0-131-88: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-network-check-target-ip-10-0-141-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "69968" uid: 828d980a-dea9-48b7-820f-740db1b5d4b3 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T14:34:57Z" message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.427µs message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:16:57Z" - latency: 1.151942ms message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 689.474µs message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 765.743µs message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 1.733334ms message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 1.024043ms message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 856.227µs message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:10:57Z" - latency: 964.937µs message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:09:57Z" - latency: 1.237026ms message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:08:57Z" - latency: 1.264789ms message: 'network-check-target-ip-10-0-141-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-network-check-target-ip-10-0-142-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "69970" uid: 00e12815-dc2c-4431-9db8-bb9bb5454163 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T14:34:57Z" message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.973216ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:16:57Z" - latency: 1.865871ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 1.975231ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 1.928312ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 2.148266ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 2.051751ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 2.122065ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:10:57Z" - latency: 1.757208ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:09:57Z" - latency: 2.097535ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:08:57Z" - latency: 1.926936ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T14:27:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-160.ec2.internal uid: ca6707ba-d43c-46a7-9c1c-bb098b29d11e resourceVersion: "68795" uid: 20308944-7224-4c25-b0d6-f60834a1ad56 spec: sourcePod: network-check-source-7d88cb55d8-kqvtj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T14:33:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.792µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:15:57Z" - latency: 1.97659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:15:57Z" - latency: 1.070369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:14:57Z" - latency: 1.773222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:14:57Z" - latency: 1.128155ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:13:57Z" - latency: 1.726818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:13:57Z" - latency: 1.028658ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:12:57Z" - latency: 2.00838ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:12:57Z" - latency: 850.72µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T15:11:57Z" - latency: 1.700726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T15:11:57Z" kind: List metadata: resourceVersion: ""