apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "18075" uid: 1a3f0160-7f0d-4e0c-8a29-37b4a5f30f03 spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T07:16:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:23:25Z" - latency: 888.326µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:22:25Z" - latency: 877.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 1.612659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 806.097µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 801.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 966.884µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 1.173179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:16:25Z" - latency: 1.012567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:15:25Z" - latency: 890.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:14:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "17413" uid: b5f384fd-6024-4754-9f49-28098f75b664 spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T07:15:25Z" message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.060754ms message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 11.056197ms message: 'load-balancer-api-external: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:21:25Z" - latency: 5.313579ms message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 8.828787ms message: 'load-balancer-api-external: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:20:25Z" - latency: 4.945995ms message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 8.030234ms message: 'load-balancer-api-external: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:19:25Z" - latency: 4.380468ms message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 8.510311ms message: 'load-balancer-api-external: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:18:25Z" - latency: 4.694285ms message: 'load-balancer-api-external: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 9.060649ms message: 'load-balancer-api-external: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "17412" uid: 4f0c9a43-3c91-4870-ae69-8192adeec86d spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T07:15:25Z" message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.741799ms message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 11.139758ms message: 'load-balancer-api-internal: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:21:25Z" - latency: 5.332038ms message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 8.928949ms message: 'load-balancer-api-internal: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:20:25Z" - latency: 4.907736ms message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 8.11522ms message: 'load-balancer-api-internal: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:19:25Z" - latency: 4.577629ms message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 8.57874ms message: 'load-balancer-api-internal: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:18:25Z" - latency: 4.030539ms message: 'load-balancer-api-internal: tcp connection to ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 9.137075ms message: 'load-balancer-api-internal: resolved host name ab9a75df1b59e4edd867261876f80afc-026d61a8e47e176d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T07:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-network-check-target-ip-10-0-133-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "18074" uid: ebca2a6a-a689-4dfa-82bb-3f4790d60b89 spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:16:25Z" message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.014509ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:23:25Z" - latency: 2.023311ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:22:25Z" - latency: 1.858567ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 2.001674ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 2.121013ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 2.041765ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 2.023481ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 2.270625ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:16:25Z" - latency: 2.548539ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:15:25Z" - latency: 2.056166ms message: 'network-check-target-ip-10-0-133-250: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:14:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-network-check-target-ip-10-0-139-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "18072" uid: 33689bac-9229-47bd-9291-1105f6aab77f spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:16:25Z" message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 847.84µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:23:25Z" - latency: 1.19324ms message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:22:25Z" - latency: 756.838µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 817.319µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 821.023µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 1.099101ms message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 767.504µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 863.518µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:16:25Z" - latency: 801.017µs message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:15:25Z" - latency: 1.06012ms message: 'network-check-target-ip-10-0-139-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:14:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-network-check-target-ip-10-0-142-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "18073" uid: 2cc5162e-9166-4db5-b722-261c026f7ad0 spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T07:16:25Z" message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.052464ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:23:25Z" - latency: 1.998769ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:22:25Z" - latency: 2.07088ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 2.270041ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 2.112963ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 2.067861ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 2.095436ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 1.725765ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:16:25Z" - latency: 2.129727ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:15:25Z" - latency: 1.949693ms message: 'network-check-target-ip-10-0-142-75: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:14:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T07:09:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-225-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-225.ec2.internal uid: 7074464c-5bfb-4d65-be8b-69433c38b1cd resourceVersion: "17411" uid: ffa53fe1-f632-4b9e-b927-f64b0e36213b spec: sourcePod: network-check-source-dbd9cf844-cg8z6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T07:15:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:21:25Z" - latency: 1.6412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:21:25Z" - latency: 868.975µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:20:25Z" - latency: 2.151303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:20:25Z" - latency: 909.653µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:19:25Z" - latency: 1.803064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:19:25Z" - latency: 733.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:18:25Z" - latency: 1.769042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:18:25Z" - latency: 883.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T07:17:25Z" - latency: 2.051462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T07:17:25Z" kind: List metadata: resourceVersion: ""