apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "39838" uid: 7f70cf86-8105-4eb0-8bad-5732d47c18f4 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:43:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 783.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:32:10Z" - latency: 914.194µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:31:10Z" - latency: 1.268387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 731.647µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 828.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 705.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 785.428µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 1.648633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:25:10Z" - latency: 1.004484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:24:10Z" - latency: 916.157µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:23:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "38739" uid: 743ad332-79fa-4ad3-9be3-b8dfb7125ba1 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:42:10Z" message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.308184ms message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 6.612519ms message: 'load-balancer-api-external: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:30:10Z" - latency: 4.06014ms message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 7.397274ms message: 'load-balancer-api-external: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:29:10Z" - latency: 3.901755ms message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 6.520965ms message: 'load-balancer-api-external: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:28:10Z" - latency: 4.757225ms message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 6.528309ms message: 'load-balancer-api-external: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:27:10Z" - latency: 5.63378ms message: 'load-balancer-api-external: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 6.818465ms message: 'load-balancer-api-external: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:26:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "38740" uid: 5bb15a93-5857-4bf7-a1ec-6a95a37acfb5 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:42:10Z" message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.29974ms message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 6.578118ms message: 'load-balancer-api-internal: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:30:10Z" - latency: 4.645765ms message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 7.366537ms message: 'load-balancer-api-internal: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:29:10Z" - latency: 3.89362ms message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 6.56512ms message: 'load-balancer-api-internal: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:28:10Z" - latency: 4.776316ms message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 6.550292ms message: 'load-balancer-api-internal: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:27:10Z" - latency: 5.643088ms message: 'load-balancer-api-internal: tcp connection to ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 6.880199ms message: 'load-balancer-api-internal: resolved host name ae1f1a3271feb41a1980454cf748c512-822044511cf00772.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:26:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-network-check-target-ip-10-0-132-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "39837" uid: 3e8bd415-c419-480f-a2ea-41789d86d045 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:43:10Z" message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.901558ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:32:10Z" - latency: 2.288532ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:31:10Z" - latency: 2.070976ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 2.192838ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 1.870918ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 2.127598ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 2.123525ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 2.157036ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:25:10Z" - latency: 1.879802ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:24:10Z" - latency: 2.292837ms message: 'network-check-target-ip-10-0-132-14: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:23:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-network-check-target-ip-10-0-139-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "39836" uid: dc386769-ee3b-4a2a-ad0e-aeb9343c36d7 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:43:10Z" message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.287409ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:32:10Z" - latency: 2.086441ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:31:10Z" - latency: 1.999513ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 2.212123ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 2.234545ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 1.801146ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 2.214108ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 2.176173ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:25:10Z" - latency: 2.071769ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:24:10Z" - latency: 1.989947ms message: 'network-check-target-ip-10-0-139-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:23:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-network-check-target-ip-10-0-139-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "39835" uid: 5789f32e-6c8c-48d4-998f-5ad65e96920f spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:43:10Z" message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 780.974µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:32:10Z" - latency: 779.224µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:31:10Z" - latency: 734.742µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 1.083821ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 675.91µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 756.952µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 918.262µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 671.954µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:25:10Z" - latency: 1.160153ms message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:24:10Z" - latency: 735.511µs message: 'network-check-target-ip-10-0-139-49: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:23:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:36:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-49-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-49.ec2.internal uid: 540d3c13-36e0-4da7-94a8-7204d8f5df68 resourceVersion: "38738" uid: 81ec2f07-5275-4373-94fe-83ec9c3914f7 spec: sourcePod: network-check-source-7b678d77c7-x86k2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:42:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 806.93µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:30:10Z" - latency: 1.856762ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:30:10Z" - latency: 743.166µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:29:10Z" - latency: 1.777849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:29:10Z" - latency: 876.006µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:28:10Z" - latency: 1.493966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:28:10Z" - latency: 802.239µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:27:10Z" - latency: 1.786759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:27:10Z" - latency: 979.982µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:26:10Z" - latency: 1.617328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:26:10Z" kind: List metadata: resourceVersion: ""