apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "55013" uid: 63628bca-2c7f-404d-82b6-d76c59574bd9 spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T14:08:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.168884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 1.690877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 1.234306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 1.732202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 1.16834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:32:53Z" - latency: 1.226869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:31:53Z" - latency: 1.246351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:30:53Z" - latency: 1.077164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:29:53Z" - latency: 961.053µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:28:53Z" - latency: 1.261883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:27:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "56227" uid: b09c1eb0-2e3d-4891-ae97-4723fc2d61d9 spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:07:53Z" message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.628121ms message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:37:53Z" - latency: 7.507393ms message: 'load-balancer-api-external: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:37:53Z" - latency: 5.113908ms message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 7.574834ms message: 'load-balancer-api-external: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:36:53Z" - latency: 5.201523ms message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 8.032087ms message: 'load-balancer-api-external: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:35:53Z" - latency: 5.501426ms message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 7.234527ms message: 'load-balancer-api-external: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:34:53Z" - latency: 5.138323ms message: 'load-balancer-api-external: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 7.20028ms message: 'load-balancer-api-external: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "56228" uid: b4dd1beb-63ea-49ed-b9fa-9439d96f7c82 spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:07:53Z" message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.653717ms message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:37:53Z" - latency: 7.525589ms message: 'load-balancer-api-internal: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:37:53Z" - latency: 5.033134ms message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 7.64177ms message: 'load-balancer-api-internal: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:36:53Z" - latency: 5.252779ms message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 7.958689ms message: 'load-balancer-api-internal: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:35:53Z" - latency: 5.498847ms message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 7.112102ms message: 'load-balancer-api-internal: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:34:53Z" - latency: 5.179085ms message: 'load-balancer-api-internal: tcp connection to aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 7.179538ms message: 'load-balancer-api-internal: resolved host name aaca34b9ffc5047f7aa5f252b918a194-5b0a103f5af6a0aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:33:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-132-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "55010" uid: c47757ab-f4c2-4f64-833b-e9e8cda47418 spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:08:53Z" message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.291µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 1.908604ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 1.422398ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 918.529µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 1.760305ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:32:53Z" - latency: 1.728567ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:31:53Z" - latency: 1.034894ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:30:53Z" - latency: 991.854µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:29:53Z" - latency: 1.474916ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:28:53Z" - latency: 1.148943ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:27:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-136-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "55011" uid: d295d78c-961c-44c3-8b1a-a63d2d3f31d5 spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:08:53Z" message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.643839ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 2.548636ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 2.417779ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 2.284119ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 2.51212ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:32:53Z" - latency: 2.481531ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:31:53Z" - latency: 2.229659ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:30:53Z" - latency: 2.320165ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:29:53Z" - latency: 2.150731ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:28:53Z" - latency: 2.242504ms message: 'network-check-target-ip-10-0-136-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:27:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-143-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "55012" uid: b9744356-812b-4438-8b3f-6aa9ebdfc16e spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:08:53Z" message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.335133ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 2.205854ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 2.067694ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 2.026845ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 2.408494ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:32:53Z" - latency: 3.772282ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:31:53Z" - latency: 2.214595ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:30:53Z" - latency: 1.894246ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:29:53Z" - latency: 1.961319ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:28:53Z" - latency: 1.697226ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:27:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:01:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: 10142287-e547-45c2-b20c-e1623a258cdf resourceVersion: "56226" uid: 1effc2ce-0947-47f0-a0ea-5de082da110e spec: sourcePod: network-check-source-869dcfcdcd-hxzgc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T14:07:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.153µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:37:53Z" - latency: 1.828873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:37:53Z" - latency: 865.776µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:36:53Z" - latency: 2.151679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:36:53Z" - latency: 1.034831ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:35:53Z" - latency: 2.29824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:35:53Z" - latency: 1.014374ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:34:53Z" - latency: 1.842195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:34:53Z" - latency: 1.014219ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:33:53Z" - latency: 2.008917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:33:53Z" kind: List metadata: resourceVersion: ""