apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "68701" uid: fb1a5b35-2a4c-4c4d-857f-bf660f6d7483 spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T18:26:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.438305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 1.183391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 821.21µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 836.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 807.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:50:17Z" - latency: 1.107245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:49:17Z" - latency: 996.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:48:17Z" - latency: 1.209992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:47:17Z" - latency: 1.052045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:46:17Z" - latency: 1.009496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "69804" uid: b557eeeb-be03-47ca-933e-d8d0f3e33bce spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T18:25:18Z" message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.786093ms message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:55:17Z" - latency: 8.877095ms message: 'load-balancer-api-external: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:55:17Z" - latency: 2.912837ms message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 7.854114ms message: 'load-balancer-api-external: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:54:17Z" - latency: 4.344719ms message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 8.649599ms message: 'load-balancer-api-external: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:53:17Z" - latency: 5.482004ms message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 9.128128ms message: 'load-balancer-api-external: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:52:17Z" - latency: 5.957125ms message: 'load-balancer-api-external: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 9.442187ms message: 'load-balancer-api-external: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "69803" uid: 7f1417b0-9aab-4ce6-85c5-958dd75b3771 spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T18:25:18Z" message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.873342ms message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:55:17Z" - latency: 8.8361ms message: 'load-balancer-api-internal: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:55:17Z" - latency: 2.827625ms message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 7.898361ms message: 'load-balancer-api-internal: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:54:17Z" - latency: 4.345034ms message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 8.689977ms message: 'load-balancer-api-internal: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:53:17Z" - latency: 5.151768ms message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 9.181656ms message: 'load-balancer-api-internal: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:52:17Z" - latency: 5.903582ms message: 'load-balancer-api-internal: tcp connection to ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 9.401899ms message: 'load-balancer-api-internal: resolved host name ac9a0d44a871b4e6c9f178c24c1ce6b3-d689397cb61722b5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T18:51:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-129-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "68698" uid: 25660d65-7c17-4475-a916-6c33677e5020 spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:26:17Z" message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 977.137µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 959.418µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 1.367072ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 849.117µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 947.508µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:50:17Z" - latency: 956.174µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:49:17Z" - latency: 1.545123ms message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:48:17Z" - latency: 908.605µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:47:17Z" - latency: 950.931µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:46:17Z" - latency: 872.086µs message: 'network-check-target-ip-10-0-129-166: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-129-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "68700" uid: ea4e2c8b-4a25-4b93-9b4d-8c805c618e89 spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:26:17Z" message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.433334ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 2.842503ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 2.433541ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 2.140423ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 2.222257ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:50:17Z" - latency: 3.303535ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:49:17Z" - latency: 2.581496ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:48:17Z" - latency: 2.403272ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:47:17Z" - latency: 2.478315ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:46:17Z" - latency: 2.42502ms message: 'network-check-target-ip-10-0-129-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-ip-10-0-138-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "68699" uid: d2898a1f-d797-432e-a7a6-b6308b0b3662 spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:26:17Z" message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.061279ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 2.47085ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 2.603103ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 2.785625ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 2.156484ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:50:17Z" - latency: 3.295414ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:49:17Z" - latency: 2.62548ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:48:17Z" - latency: 2.42567ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:47:17Z" - latency: 2.472084ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:46:17Z" - latency: 2.303721ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:45:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:19:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-166-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-166.ec2.internal uid: 894023ad-8b6b-4843-b096-f29cfea70d03 resourceVersion: "69802" uid: a64b1980-9c6f-4c90-94c0-bd37ba148bba spec: sourcePod: network-check-source-6f8b768455-hdczs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T18:25:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.351852ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:55:17Z" - latency: 1.965871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:55:17Z" - latency: 882.135µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:54:17Z" - latency: 1.879165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:54:17Z" - latency: 930.657µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:53:17Z" - latency: 1.817221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:53:17Z" - latency: 992.793µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:52:17Z" - latency: 1.833178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:52:17Z" - latency: 1.136429ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T18:51:17Z" - latency: 1.908348ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T18:51:17Z" kind: List metadata: resourceVersion: ""