apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "78552" uid: cffc1e42-653e-4332-9e18-9a52df408d58 spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T16:34:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.897µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:23:04Z" - latency: 1.101551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:22:04Z" - latency: 997.227µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 1.024466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 942.749µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 1.022069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 1.226137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 1.316096ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:16:04Z" - latency: 1.076785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:15:04Z" - latency: 1.571018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "76551" uid: 0192352b-91da-483d-b1d0-264e1a96b5a6 spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T16:33:04Z" message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.400035ms message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 7.753613ms message: 'load-balancer-api-external: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:21:04Z" - latency: 5.79385ms message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 9.348962ms message: 'load-balancer-api-external: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:20:04Z" - latency: 5.832964ms message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 11.036056ms message: 'load-balancer-api-external: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:19:04Z" - latency: 5.243204ms message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 10.93201ms message: 'load-balancer-api-external: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:18:04Z" - latency: 5.347131ms message: 'load-balancer-api-external: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 16.002785ms message: 'load-balancer-api-external: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "76552" uid: 6b2e3352-f31f-44fc-8084-9b14071d7d9a spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T16:33:04Z" message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.218202ms message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 7.793437ms message: 'load-balancer-api-internal: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:21:04Z" - latency: 5.502983ms message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 9.42672ms message: 'load-balancer-api-internal: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:20:04Z" - latency: 11.945914ms message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 11.06653ms message: 'load-balancer-api-internal: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:19:04Z" - latency: 5.240313ms message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 11.022298ms message: 'load-balancer-api-internal: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:18:04Z" - latency: 5.270964ms message: 'load-balancer-api-internal: tcp connection to a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 16.033766ms message: 'load-balancer-api-internal: resolved host name a2a6ebcb1121f4219a48f6ba691c728f-e971ee750c1099fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-128-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "78551" uid: 54c31ac1-97eb-4fb3-b8b5-54e7e3fafd6d spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:34:04Z" message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.559586ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:23:04Z" - latency: 2.936647ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:22:04Z" - latency: 2.400674ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 2.311806ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 2.302158ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 2.431219ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 2.409045ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 2.744072ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:16:04Z" - latency: 2.521036ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:15:04Z" - latency: 2.637795ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-128-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "78549" uid: 87b4ff4f-6693-4e6a-abd7-c1af78318b2d spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:34:04Z" message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.108765ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:23:04Z" - latency: 991.506µs message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:22:04Z" - latency: 1.049779ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 1.2121ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 989.121µs message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 1.26436ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 1.470359ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 1.550578ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:16:04Z" - latency: 1.251755ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:15:04Z" - latency: 1.123848ms message: 'network-check-target-ip-10-0-128-82: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-network-check-target-ip-10-0-131-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "78550" uid: 28d5dbf4-ba25-4fd3-b2b7-05406043a3d8 spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T16:34:04Z" message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.061986ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:23:04Z" - latency: 2.82782ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:22:04Z" - latency: 2.359952ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 2.474173ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 2.234982ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 3.064619ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 2.717974ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 2.472752ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:16:04Z" - latency: 2.518352ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:15:04Z" - latency: 2.378131ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:14:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T16:27:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-82-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-82.ec2.internal uid: 7c1fbc9d-6ca5-456a-8517-a22df0eeedb9 resourceVersion: "76550" uid: f2f05d8f-941f-4794-97cc-021d0a229e86 spec: sourcePod: network-check-source-65bdbbff45-t78sc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T16:33:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.200052ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:21:04Z" - latency: 1.906296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:21:04Z" - latency: 765.628µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:20:04Z" - latency: 2.398795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:20:04Z" - latency: 992.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:19:04Z" - latency: 2.220519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:19:04Z" - latency: 1.342619ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:18:04Z" - latency: 1.960565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:18:04Z" - latency: 866.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:17:04Z" - latency: 1.857115ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:17:04Z" kind: List metadata: resourceVersion: ""