apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "19227" uid: 0d23dfa4-f4c2-4754-84e6-b7692fb2d376 spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T16:10:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 957.966µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 1.131277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:22:34Z" - latency: 986.696µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:21:34Z" - latency: 787.483µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:20:34Z" - latency: 1.192539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:19:34Z" - latency: 1.087566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:18:34Z" - latency: 833.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:17:34Z" - latency: 844.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:16:34Z" - latency: 947.977µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:15:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "20379" uid: 9d964b07-2b9d-49d9-9c88-7a4b6167a880 spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T16:09:34Z" message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.145027ms message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:34Z" - latency: 9.309527ms message: 'load-balancer-api-external: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:27:34Z" - latency: 4.779362ms message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:34Z" - latency: 14.903556ms message: 'load-balancer-api-external: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:26:34Z" - latency: 4.765008ms message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:34Z" - latency: 6.855761ms message: 'load-balancer-api-external: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:25:34Z" - latency: 6.078957ms message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 8.705358ms message: 'load-balancer-api-external: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:24:34Z" - latency: 5.209899ms message: 'load-balancer-api-external: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 5.947019ms message: 'load-balancer-api-external: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:23:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "20378" uid: 8f09b994-35c6-4f09-a3ee-dae9af1f71ac spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T16:09:34Z" message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.117184ms message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:34Z" - latency: 9.25732ms message: 'load-balancer-api-internal: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:27:34Z" - latency: 4.750072ms message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:34Z" - latency: 15.018304ms message: 'load-balancer-api-internal: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:26:34Z" - latency: 4.780353ms message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:34Z" - latency: 6.761211ms message: 'load-balancer-api-internal: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:25:34Z" - latency: 5.181455ms message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 8.819618ms message: 'load-balancer-api-internal: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:24:34Z" - latency: 5.15349ms message: 'load-balancer-api-internal: tcp connection to a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 6.013971ms message: 'load-balancer-api-internal: resolved host name a74c1958ef1904071a8c9e93d0608dcf-c4b978196bd0a968.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T16:23:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-network-check-target-ip-10-0-129-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "19226" uid: b23e8c4b-5314-4a5b-8261-9c6419268583 spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:10:34Z" message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.187122ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 1.80168ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 1.74442ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:22:34Z" - latency: 1.921959ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:21:34Z" - latency: 1.693313ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:20:34Z" - latency: 1.798002ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:19:34Z" - latency: 2.323839ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:18:34Z" - latency: 1.827444ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:17:34Z" - latency: 1.903593ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:16:34Z" - latency: 1.679265ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:15:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-network-check-target-ip-10-0-133-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "19225" uid: a744b1fa-3bb2-4f07-86de-33b0ef63503e spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:10:34Z" message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189649ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 2.129959ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 2.127854ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:22:34Z" - latency: 2.335576ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:21:34Z" - latency: 2.038575ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:20:34Z" - latency: 2.173419ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:19:34Z" - latency: 2.512706ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:18:34Z" - latency: 2.226469ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:17:34Z" - latency: 2.206031ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:16:34Z" - latency: 2.113962ms message: 'network-check-target-ip-10-0-133-120: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:15:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-network-check-target-ip-10-0-140-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "19224" uid: f57d16a4-e39b-4f16-961b-af2ad19d4de4 spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T16:10:34Z" message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.495099ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 1.092586ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 866.714µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:22:34Z" - latency: 776.403µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:21:34Z" - latency: 1.109645ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:20:34Z" - latency: 812.038µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:19:34Z" - latency: 840.139µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:18:34Z" - latency: 823.836µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:17:34Z" - latency: 786.819µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:16:34Z" - latency: 938.325µs message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:15:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T16:03:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-195.ec2.internal uid: 6ca3cc96-f3c8-468b-87b7-6e88c8cb9e63 resourceVersion: "20377" uid: 9b7fa47b-1287-467b-bf3e-3e86fbce8496 spec: sourcePod: network-check-source-7f44b6dd87-tw7kn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T16:09:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.355µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:27:34Z" - latency: 1.58458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:27:34Z" - latency: 736.835µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:26:34Z" - latency: 1.413333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:26:34Z" - latency: 795.108µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:25:34Z" - latency: 1.623289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:25:34Z" - latency: 791.994µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:24:34Z" - latency: 2.230889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:24:34Z" - latency: 846.127µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T16:23:34Z" - latency: 1.773783ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T16:23:34Z" kind: List metadata: resourceVersion: ""