apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "21330" uid: b9e24d3a-f1bb-4716-9171-a8e21d3723bb spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T01:23:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.726µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 912.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 1.221105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 956.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:41:07Z" - latency: 881.076µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:40:07Z" - latency: 1.146683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:39:07Z" - latency: 838.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:38:07Z" - latency: 1.160656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:37:07Z" - latency: 958.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:36:07Z" - latency: 795.765µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "22296" uid: 61411788-8def-4644-9d10-020295de2092 spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T01:22:07Z" message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.754279ms message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:46:07Z" - latency: 7.781396ms message: 'load-balancer-api-external: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:46:07Z" - latency: 5.367997ms message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:45:07Z" - latency: 7.948039ms message: 'load-balancer-api-external: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:45:07Z" - latency: 4.945008ms message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 8.049055ms message: 'load-balancer-api-external: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:44:07Z" - latency: 4.090161ms message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 9.356898ms message: 'load-balancer-api-external: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:43:07Z" - latency: 4.332197ms message: 'load-balancer-api-external: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 8.279852ms message: 'load-balancer-api-external: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:42:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "22295" uid: f92f18ca-13c6-4e14-8195-5fe337dd8727 spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T01:22:07Z" message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.753263ms message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:46:07Z" - latency: 7.819038ms message: 'load-balancer-api-internal: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:46:07Z" - latency: 5.332847ms message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:45:07Z" - latency: 8.030245ms message: 'load-balancer-api-internal: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:45:07Z" - latency: 5.009623ms message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 7.920119ms message: 'load-balancer-api-internal: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:44:07Z" - latency: 5.519815ms message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 9.443233ms message: 'load-balancer-api-internal: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:43:07Z" - latency: 5.254704ms message: 'load-balancer-api-internal: tcp connection to a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 8.223775ms message: 'load-balancer-api-internal: resolved host name a731dc1654a51486588ae83bcc759ec5-28ce99c307964145.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T01:42:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-network-check-target-ip-10-0-137-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "21327" uid: 4196106f-99f8-470a-93d4-c0230da2b34b spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T01:23:07Z" message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.757µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 830.463µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 741.622µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 1.394253ms message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:41:07Z" - latency: 883.205µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:40:07Z" - latency: 1.271425ms message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:39:07Z" - latency: 822.096µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:38:07Z" - latency: 869.176µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:37:07Z" - latency: 1.188024ms message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:36:07Z" - latency: 793.083µs message: 'network-check-target-ip-10-0-137-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-network-check-target-ip-10-0-140-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "21329" uid: 58802413-6f2e-4ed8-8011-d15a9705ef89 spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T01:23:07Z" message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.188154ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 2.259899ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 2.410977ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 1.945749ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:41:07Z" - latency: 2.086819ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:40:07Z" - latency: 2.817007ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:39:07Z" - latency: 2.230191ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:38:07Z" - latency: 2.165926ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:37:07Z" - latency: 1.939155ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:36:07Z" - latency: 2.54938ms message: 'network-check-target-ip-10-0-140-41: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-network-check-target-ip-10-0-143-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "21328" uid: d5827447-d185-42e9-b438-ba0e4acbd06d spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T01:23:07Z" message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.045476ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 2.169143ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 1.934553ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 2.054854ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:41:07Z" - latency: 2.11695ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:40:07Z" - latency: 2.02347ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:39:07Z" - latency: 2.181076ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:38:07Z" - latency: 1.984322ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:37:07Z" - latency: 1.854183ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:36:07Z" - latency: 2.26782ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:35:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T01:16:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-202.ec2.internal uid: 5924db9a-abba-4581-a803-974c5364da2e resourceVersion: "22294" uid: d1f27608-85ec-494f-b8bf-2fee4074ffe6 spec: sourcePod: network-check-source-7f44b6dd87-mfg9l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T01:22:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:46:07Z" - latency: 1.821393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T01:46:07Z" - latency: 846.655µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:45:07Z" - latency: 1.690572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T01:45:07Z" - latency: 804.828µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:44:07Z" - latency: 1.886896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T01:44:07Z" - latency: 851.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:43:07Z" - latency: 1.718291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T01:43:07Z" - latency: 892.655µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T01:42:07Z" - latency: 1.677355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T01:42:07Z" kind: List metadata: resourceVersion: ""