apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "75311" uid: d4f4894c-0737-461b-bc94-ce0b8d4fc574 spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T18:41:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.107218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:30:56Z" - latency: 1.112062ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:29:56Z" - latency: 1.157834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 920.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 925.523µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 1.244377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 1.110512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 1.075713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:56Z" - latency: 1.242989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:56Z" - latency: 863.736µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "71731" uid: c4d02fba-be88-49b9-a08f-e5b0efd69855 spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T18:40:56Z" message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.998561ms message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 8.110029ms message: 'load-balancer-api-external: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:28:56Z" - latency: 5.506024ms message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 7.24209ms message: 'load-balancer-api-external: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:56Z" - latency: 4.072338ms message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 7.606387ms message: 'load-balancer-api-external: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:56Z" - latency: 4.786781ms message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 6.971467ms message: 'load-balancer-api-external: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:56Z" - latency: 4.784244ms message: 'load-balancer-api-external: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 10.17928ms message: 'load-balancer-api-external: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "71730" uid: 61072375-9dad-4b79-bbb9-44ab662cec4d spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T18:40:56Z" message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.839878ms message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 8.219544ms message: 'load-balancer-api-internal: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:28:56Z" - latency: 5.267097ms message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 7.192019ms message: 'load-balancer-api-internal: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:56Z" - latency: 3.643488ms message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 7.692434ms message: 'load-balancer-api-internal: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:56Z" - latency: 4.647007ms message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 6.914817ms message: 'load-balancer-api-internal: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:56Z" - latency: 5.163995ms message: 'load-balancer-api-internal: tcp connection to af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 10.225873ms message: 'load-balancer-api-internal: resolved host name af4465645c4f744a9b27c242e702f479-261a07a8ba5b11c6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-network-check-target-ip-10-0-131-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "75313" uid: 237ae148-4906-4b8d-b5ff-58ef16328fa7 spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:41:56Z" message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.152584ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:30:56Z" - latency: 2.293412ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:29:56Z" - latency: 2.042016ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 7.5398ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 2.223647ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 2.26162ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 2.303982ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 2.183921ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:56Z" - latency: 2.198024ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:56Z" - latency: 2.058798ms message: 'network-check-target-ip-10-0-131-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-network-check-target-ip-10-0-132-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "75310" uid: 3917299f-9fac-4772-94c2-b7ccb8680ac0 spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:41:56Z" message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.388µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:30:56Z" - latency: 889.317µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:29:56Z" - latency: 906.132µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 1.456504ms message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 1.574569ms message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 916.836µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 958.741µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 1.248526ms message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:56Z" - latency: 820.199µs message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:56Z" - latency: 1.745529ms message: 'network-check-target-ip-10-0-132-186: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-network-check-target-ip-10-0-140-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "75312" uid: ad63d340-9633-4b41-8225-fad829a16ac0 spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:41:56Z" message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.419282ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:30:56Z" - latency: 2.444316ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:29:56Z" - latency: 2.016224ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 7.475892ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 1.840199ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 2.111665ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 2.435281ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 2.32691ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:56Z" - latency: 2.21623ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:56Z" - latency: 2.485218ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:34:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-186.ec2.internal uid: 8358360e-fa40-4f64-8b9d-eec467bec392 resourceVersion: "71728" uid: a2d87d9c-de80-4b59-a438-bf02b86f374e spec: sourcePod: network-check-source-7d88cb55d8-phqs2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T18:40:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.049µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:28:56Z" - latency: 2.059312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:28:56Z" - latency: 6.652212ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:56Z" - latency: 1.866099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:56Z" - latency: 942.333µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:56Z" - latency: 1.813728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:56Z" - latency: 1.053285ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:56Z" - latency: 1.736511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:56Z" - latency: 806.994µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:56Z" - latency: 1.718082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:56Z" kind: List metadata: resourceVersion: ""