apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "71781" uid: 7b7dd3a4-69c7-4326-8c8c-0bc4c17977d9 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:38:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.325976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:20:29Z" - latency: 994.688µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:19:29Z" - latency: 1.188659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:18:29Z" - latency: 1.234629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:17:29Z" - latency: 1.050196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:16:29Z" - latency: 1.506192ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:15:29Z" - latency: 914.452µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:14:29Z" - latency: 1.285897ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:13:29Z" - latency: 1.462784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:12:29Z" - latency: 933.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:11:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "77055" uid: 11b47295-728b-4f6a-9c29-4b51d0a77ce2 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:37:29Z" message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.138741ms message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:25:29Z" - latency: 9.282377ms message: 'load-balancer-api-external: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:25:29Z" - latency: 4.983237ms message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:24:29Z" - latency: 7.183199ms message: 'load-balancer-api-external: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:24:29Z" - latency: 4.97557ms message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:23:29Z" - latency: 6.781255ms message: 'load-balancer-api-external: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:23:29Z" - latency: 5.071236ms message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:22:29Z" - latency: 6.611975ms message: 'load-balancer-api-external: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:22:29Z" - latency: 8.116501ms message: 'load-balancer-api-external: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:21:29Z" - latency: 6.56924ms message: 'load-balancer-api-external: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:21:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "77056" uid: fdf2a083-9088-426a-a432-fe047d7a60c8 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:37:29Z" message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.117484ms message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:25:29Z" - latency: 9.355196ms message: 'load-balancer-api-internal: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:25:29Z" - latency: 5.082114ms message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:24:29Z" - latency: 7.156596ms message: 'load-balancer-api-internal: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:24:29Z" - latency: 4.999335ms message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:23:29Z" - latency: 6.811254ms message: 'load-balancer-api-internal: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:23:29Z" - latency: 4.188299ms message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:22:29Z" - latency: 6.703165ms message: 'load-balancer-api-internal: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:22:29Z" - latency: 4.594091ms message: 'load-balancer-api-internal: tcp connection to af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:21:29Z" - latency: 6.536545ms message: 'load-balancer-api-internal: resolved host name af5f8bacc7ded4f1c887d66eadefeb76-a9cefc03ca6fa805.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:21:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-128-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "71779" uid: 7798b8fd-da5d-4b17-8ee8-2cb18f19cbfb spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:38:29Z" message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.194544ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:20:29Z" - latency: 2.260499ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:19:29Z" - latency: 2.439651ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:18:29Z" - latency: 2.540384ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:17:29Z" - latency: 2.439553ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:16:29Z" - latency: 2.65909ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:15:29Z" - latency: 2.269684ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:14:29Z" - latency: 3.011413ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:13:29Z" - latency: 2.333552ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:12:29Z" - latency: 2.080574ms message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:11:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-132-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "71778" uid: 44a9d1b9-c83d-40ee-8d5c-8589d28799f3 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:38:29Z" message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.520468ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:20:29Z" - latency: 990.816µs message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:19:29Z" - latency: 1.053001ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:18:29Z" - latency: 1.002941ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:17:29Z" - latency: 1.475648ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:16:29Z" - latency: 1.026079ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:15:29Z" - latency: 922.518µs message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:14:29Z" - latency: 1.09578ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:13:29Z" - latency: 1.658512ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:12:29Z" - latency: 1.49732ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:11:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-137-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "71780" uid: 844944f0-2a3f-40b7-8e91-d832fbdecfd6 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:38:29Z" message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316043ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:20:29Z" - latency: 2.40191ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:19:29Z" - latency: 2.566159ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:18:29Z" - latency: 2.704286ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:17:29Z" - latency: 2.559802ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:16:29Z" - latency: 2.524564ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:15:29Z" - latency: 2.463492ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:14:29Z" - latency: 2.712303ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:13:29Z" - latency: 2.329928ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:12:29Z" - latency: 2.358968ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:11:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.ec2.internal uid: 8f284d98-5e96-4f44-b9ce-90a4e9be8b1b resourceVersion: "77054" uid: 8b9c727a-8605-4c33-9c47-e905b4a100d4 spec: sourcePod: network-check-source-65bdbbff45-ckj9k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:37:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.288433ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:25:29Z" - latency: 1.899265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:25:29Z" - latency: 810.679µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:24:29Z" - latency: 1.923329ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:24:29Z" - latency: 920.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:23:29Z" - latency: 2.078041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:23:29Z" - latency: 1.248657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:22:29Z" - latency: 1.921513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:22:29Z" - latency: 903.883µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:21:29Z" - latency: 1.8679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:21:29Z" kind: List metadata: resourceVersion: ""