apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32549" uid: 72963f49-665c-4798-8d0c-539c274875f1 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T11:51:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.032505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 890.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 1.029726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 1.021281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 1.021288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 1.225569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:21:21Z" - latency: 960.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:20:21Z" - latency: 1.119703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:19:21Z" - latency: 1.102074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:18:21Z" - latency: 1.151083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:17:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32550" uid: 190f3ea7-2b4c-489b-85c0-8d64ae0bc726 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:50:21Z" message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.637002ms message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 8.824546ms message: 'load-balancer-api-external: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:26:21Z" - latency: 4.854617ms message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 8.078932ms message: 'load-balancer-api-external: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:25:21Z" - latency: 4.92046ms message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 10.13392ms message: 'load-balancer-api-external: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:24:21Z" - latency: 6.013712ms message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 8.928677ms message: 'load-balancer-api-external: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:23:21Z" - latency: 6.646466ms message: 'load-balancer-api-external: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 14.149112ms message: 'load-balancer-api-external: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:22:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32551" uid: c3a14d92-3e9a-4709-b730-481cc00cf7a8 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:50:21Z" message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.726933ms message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 8.921877ms message: 'load-balancer-api-internal: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:26:21Z" - latency: 4.8458ms message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 8.205301ms message: 'load-balancer-api-internal: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:25:21Z" - latency: 4.800035ms message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 10.229972ms message: 'load-balancer-api-internal: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:24:21Z" - latency: 4.958577ms message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 8.998413ms message: 'load-balancer-api-internal: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:23:21Z" - latency: 6.12307ms message: 'load-balancer-api-internal: tcp connection to abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 14.228256ms message: 'load-balancer-api-internal: resolved host name abafdbec7c5854945bb9d44ac0d50f5e-49c29facbc6c521d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T12:22:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-135-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32545" uid: ed8e38f2-3006-4469-b207-72b12811eea4 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:51:21Z" message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.36331ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 1.436479ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 889.924µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 852.208µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 889.702µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 984.339µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:21:21Z" - latency: 1.029616ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:20:21Z" - latency: 1.557773ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:19:21Z" - latency: 914.68µs message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:18:21Z" - latency: 1.409474ms message: 'network-check-target-ip-10-0-135-101: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:17:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-138-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32546" uid: 0445e9a4-db82-494f-927c-d23ccc212725 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:51:21Z" message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.385958ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 2.490746ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 2.254279ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 1.909811ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 2.356965ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 2.310906ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:21:21Z" - latency: 2.366394ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:20:21Z" - latency: 2.406082ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:19:21Z" - latency: 2.441079ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:18:21Z" - latency: 1.986809ms message: 'network-check-target-ip-10-0-138-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:17:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-ip-10-0-140-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32548" uid: 30005a5f-e7aa-4cbe-8802-91c8200ab645 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:51:21Z" message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.054965ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 2.389086ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 2.003821ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 1.881586ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 2.224808ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 2.461926ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:21:21Z" - latency: 2.750814ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:20:21Z" - latency: 2.415348ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:19:21Z" - latency: 2.082812ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:18:21Z" - latency: 2.385324ms message: 'network-check-target-ip-10-0-140-177: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:17:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:44:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-101.ec2.internal uid: ed154bd2-f5e8-4278-bfb2-d9fb42766bd2 resourceVersion: "32547" uid: 884b5323-33a6-4980-a75d-5c89df62ca21 spec: sourcePod: network-check-source-989f8b8dc-smskv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T11:50:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.028391ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:26:21Z" - latency: 1.699796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T12:26:21Z" - latency: 844.249µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:25:21Z" - latency: 1.497901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T12:25:21Z" - latency: 841.748µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:24:21Z" - latency: 1.586669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T12:24:21Z" - latency: 766.944µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:23:21Z" - latency: 1.709615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T12:23:21Z" - latency: 841.668µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T12:22:21Z" - latency: 1.64565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T12:22:21Z" kind: List metadata: resourceVersion: ""