apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "44110" uid: 610d176e-79f7-4bff-8132-87c82216bbe4 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T00:58:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 1.069554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 1.104284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 1.080264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:16:15Z" - latency: 1.099611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:15:15Z" - latency: 1.132666ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:14:15Z" - latency: 1.298189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:13:15Z" - latency: 957.424µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:12:15Z" - latency: 901.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:11:15Z" - latency: 786.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "46686" uid: 250e4af9-187f-4986-869a-580abbc53ef0 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T00:57:15Z" message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.337525ms message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:21:15Z" - latency: 12.620631ms message: 'load-balancer-api-external: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:21:15Z" - latency: 4.45645ms message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:20:15Z" - latency: 9.095641ms message: 'load-balancer-api-external: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:20:15Z" - latency: 4.690214ms message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 8.221361ms message: 'load-balancer-api-external: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:19:15Z" - latency: 5.663703ms message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 7.383833ms message: 'load-balancer-api-external: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:18:15Z" - latency: 4.341405ms message: 'load-balancer-api-external: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 7.673921ms message: 'load-balancer-api-external: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:17:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "46685" uid: b233668b-1d3e-42a7-be18-ce182d663329 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T00:57:15Z" message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.584665ms message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:21:15Z" - latency: 12.652004ms message: 'load-balancer-api-internal: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:21:15Z" - latency: 4.455306ms message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:20:15Z" - latency: 9.046876ms message: 'load-balancer-api-internal: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:20:15Z" - latency: 4.893978ms message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 8.180658ms message: 'load-balancer-api-internal: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:19:15Z" - latency: 5.094086ms message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 7.417172ms message: 'load-balancer-api-internal: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:18:15Z" - latency: 4.355076ms message: 'load-balancer-api-internal: tcp connection to aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 7.80285ms message: 'load-balancer-api-internal: resolved host name aea745e4310c548baa67afb9917fe699-c13df39f8deab48a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T01:17:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-network-check-target-ip-10-0-131-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "44106" uid: 5e61644d-950d-49d7-b906-76f16e32717b spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T00:58:15Z" message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.104µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 937.502µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 1.366477ms message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 889.03µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:16:15Z" - latency: 1.279002ms message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:15:15Z" - latency: 915.865µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:14:15Z" - latency: 1.212816ms message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:13:15Z" - latency: 850.732µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:12:15Z" - latency: 811.83µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:11:15Z" - latency: 803.587µs message: 'network-check-target-ip-10-0-131-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-network-check-target-ip-10-0-140-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "44107" uid: c20ad564-b7b0-44fb-82e3-f83ec127d932 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T00:58:15Z" message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.20013ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 2.288647ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 2.915097ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 2.339696ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:16:15Z" - latency: 2.264531ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:15:15Z" - latency: 2.91372ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:14:15Z" - latency: 2.29127ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:13:15Z" - latency: 2.279825ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:12:15Z" - latency: 2.352498ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:11:15Z" - latency: 2.115574ms message: 'network-check-target-ip-10-0-140-228: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-network-check-target-ip-10-0-141-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "44108" uid: 5501ba4a-8700-41fb-9bb4-10770031fc79 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T00:58:15Z" message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.724983ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 2.190652ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 2.046646ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 1.940742ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:16:15Z" - latency: 2.174848ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:15:15Z" - latency: 2.052101ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:14:15Z" - latency: 2.151582ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:13:15Z" - latency: 1.832663ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:12:15Z" - latency: 1.965938ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:11:15Z" - latency: 1.535707ms message: 'network-check-target-ip-10-0-141-236: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:10:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T00:51:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-222-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-222.ec2.internal uid: 48fc32d3-34dd-4cfb-9e64-44550b2caa63 resourceVersion: "46683" uid: 5f72a32b-0cc8-45ed-8399-22185bf116a9 spec: sourcePod: network-check-source-7f44b6dd87-4pfg9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T00:57:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.137932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:21:15Z" - latency: 1.673108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T01:21:15Z" - latency: 977.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:20:15Z" - latency: 1.605918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T01:20:15Z" - latency: 799.78µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:19:15Z" - latency: 1.837414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T01:19:15Z" - latency: 868.786µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:18:15Z" - latency: 1.63974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T01:18:15Z" - latency: 1.342933ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T01:17:15Z" - latency: 1.970786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T01:17:15Z" kind: List metadata: resourceVersion: ""