apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "55934" uid: 1738e7be-918d-4391-af0e-00e7a6af5493 spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T02:52:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 989.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 1.478218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 1.067392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 1.102492ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 1.137282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:16:45Z" - latency: 1.594843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:15:45Z" - latency: 1.446175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:14:45Z" - latency: 977.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:13:45Z" - latency: 994.809µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:12:45Z" - latency: 956.698µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:11:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "57022" uid: 8b645d97-3671-4ec0-9a17-8127c6fb243c spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T02:51:45Z" message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.009341ms message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:21:45Z" - latency: 8.432031ms message: 'load-balancer-api-external: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:21:45Z" - latency: 5.179627ms message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 8.963676ms message: 'load-balancer-api-external: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:20:45Z" - latency: 5.033999ms message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 7.882106ms message: 'load-balancer-api-external: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:19:45Z" - latency: 4.472739ms message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 11.776737ms message: 'load-balancer-api-external: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:18:45Z" - latency: 4.425099ms message: 'load-balancer-api-external: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 14.887146ms message: 'load-balancer-api-external: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:17:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "57021" uid: eee39ce3-b4a9-4745-a3d7-130ff5e64518 spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T02:51:45Z" message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.010748ms message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:21:45Z" - latency: 8.365545ms message: 'load-balancer-api-internal: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:21:45Z" - latency: 4.69253ms message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 8.992691ms message: 'load-balancer-api-internal: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:20:45Z" - latency: 5.041749ms message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 7.778662ms message: 'load-balancer-api-internal: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:19:45Z" - latency: 4.412748ms message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 11.865526ms message: 'load-balancer-api-internal: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:18:45Z" - latency: 4.321999ms message: 'load-balancer-api-internal: tcp connection to a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 14.786027ms message: 'load-balancer-api-internal: resolved host name a3dfb5252973848c0b7358566cc67b49-84ee2615f5123c44.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T03:17:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-131-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "55931" uid: e32ec25e-089b-4867-9cc6-72720b4ea490 spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T02:52:45Z" message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.835µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 902.926µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 855.366µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 918.185µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 1.680862ms message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:16:45Z" - latency: 838.701µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:15:45Z" - latency: 937.15µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:14:45Z" - latency: 762.016µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:13:45Z" - latency: 779.364µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:12:45Z" - latency: 715.155µs message: 'network-check-target-ip-10-0-131-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:11:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-139-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "55933" uid: 9dadce00-397e-4339-9040-afab6ba220d8 spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T02:52:45Z" message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.17774ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 2.028234ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 2.507472ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 2.162442ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 2.384256ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:16:45Z" - latency: 2.482375ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:15:45Z" - latency: 2.221021ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:14:45Z" - latency: 2.033926ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:13:45Z" - latency: 2.12568ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:12:45Z" - latency: 2.095195ms message: 'network-check-target-ip-10-0-139-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:11:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-network-check-target-ip-10-0-139-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "55932" uid: f14fb494-b975-479a-bd1a-058b1aaabfff spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T02:52:45Z" message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.822438ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 1.966329ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 1.689825ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 1.960005ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 2.337314ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:16:45Z" - latency: 1.708141ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:15:45Z" - latency: 1.882879ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:14:45Z" - latency: 2.093066ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:13:45Z" - latency: 2.110924ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:12:45Z" - latency: 2.072218ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:11:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T02:45:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-238-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-238.ec2.internal uid: 977bec81-35a6-4df5-b689-4072ab1be662 resourceVersion: "57020" uid: 1b5b5ca8-8f96-42de-bd88-49b1b00c10bb spec: sourcePod: network-check-source-989f8b8dc-j7prq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T02:51:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.073µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:21:45Z" - latency: 1.824802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T03:21:45Z" - latency: 876.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:20:45Z" - latency: 1.87576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T03:20:45Z" - latency: 814.969µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:19:45Z" - latency: 1.930774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T03:19:45Z" - latency: 861.615µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:18:45Z" - latency: 1.521561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T03:18:45Z" - latency: 862.796µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T03:17:45Z" - latency: 1.672945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T03:17:45Z" kind: List metadata: resourceVersion: ""