apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "71251" uid: 98596bfc-1ef7-4286-bfc0-8f0629f00bbe spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T11:45:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.878µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:35Z" - latency: 1.29688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 1.014899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 866.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 1.501769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 760.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 776.115µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:21:35Z" - latency: 1.643738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:20:35Z" - latency: 1.002375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:19:35Z" - latency: 949.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "70063" uid: b080f29b-e792-474f-810b-8b582b36324f spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T11:44:35Z" message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.823503ms message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 8.819713ms message: 'load-balancer-api-external: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:26:35Z" - latency: 3.414299ms message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 6.988598ms message: 'load-balancer-api-external: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:25:35Z" - latency: 5.319441ms message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 8.654722ms message: 'load-balancer-api-external: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:24:35Z" - latency: 4.64176ms message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 10.609014ms message: 'load-balancer-api-external: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:23:35Z" - latency: 5.884696ms message: 'load-balancer-api-external: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 7.789162ms message: 'load-balancer-api-external: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:22:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "70062" uid: 8e5e5051-ca16-4932-8042-1fd266cceb07 spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T11:44:35Z" message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.361034ms message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 8.876139ms message: 'load-balancer-api-internal: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:26:35Z" - latency: 3.576448ms message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 6.972545ms message: 'load-balancer-api-internal: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:25:35Z" - latency: 3.48635ms message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 8.699452ms message: 'load-balancer-api-internal: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:24:35Z" - latency: 4.687378ms message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 10.579991ms message: 'load-balancer-api-internal: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:23:35Z" - latency: 4.365163ms message: 'load-balancer-api-internal: tcp connection to a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 7.843616ms message: 'load-balancer-api-internal: resolved host name a4e5e55fa4e4d4ccda54cdd996967e25-b1268de527a23bfd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T12:22:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-130-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "71248" uid: f6815d6c-1875-4ee0-abd8-80528acd073b spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:45:35Z" message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.367614ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:35Z" - latency: 1.264086ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 969.034µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 949.019µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 765.66µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 1.85193ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 1.144546ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:21:35Z" - latency: 1.39651ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:20:35Z" - latency: 914.23µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:19:35Z" - latency: 1.100343ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-141-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "71249" uid: 84f26cbf-5eb6-452e-9868-067ad603e7b6 spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:45:35Z" message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.792675ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:35Z" - latency: 2.01205ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 2.055809ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 1.839577ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 1.962945ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 2.48474ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 1.965906ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:21:35Z" - latency: 2.34059ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:20:35Z" - latency: 1.861837ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:19:35Z" - latency: 2.068965ms message: 'network-check-target-ip-10-0-141-155: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-142-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "71250" uid: afd65bdc-2ff8-4bed-8705-2690461193c7 spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:45:35Z" message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.081507ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:27:35Z" - latency: 2.317816ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 2.472614ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 2.22496ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 2.205204ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 2.437789ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 2.379214ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:21:35Z" - latency: 1.81492ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:20:35Z" - latency: 2.193578ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:19:35Z" - latency: 2.619316ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:38:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: a13fbd56-0f49-4eb2-817a-e365d7667cb7 resourceVersion: "70061" uid: 558a010e-ec06-4e2d-b4d6-633dafeef96f spec: sourcePod: network-check-source-7d88cb55d8-9lgq9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T11:44:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.176µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:26:35Z" - latency: 1.750356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:26:35Z" - latency: 986.005µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:25:35Z" - latency: 1.856241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:25:35Z" - latency: 900.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:24:35Z" - latency: 1.54389ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:24:35Z" - latency: 814.743µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:23:35Z" - latency: 1.803053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:23:35Z" - latency: 905.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:22:35Z" - latency: 2.466334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T12:22:35Z" kind: List metadata: resourceVersion: ""