apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "18737" uid: a255b7b1-6310-4365-b755-ad97d2a1f02d spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T18:05:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 836.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 806.582µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:11Z" - latency: 924.89µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:11Z" - latency: 1.140738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:11Z" - latency: 931.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:11Z" - latency: 953.095µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:11Z" - latency: 905.186µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:11Z" - latency: 1.106372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:11Z" - latency: 903.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:04:11Z" - latency: 844.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "20851" uid: 133fcf92-27ac-41e3-aee8-bcb291cf9ed0 spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:04:11Z" message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.533807ms message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:11Z" - latency: 7.296307ms message: 'load-balancer-api-external: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:11Z" - latency: 6.17557ms message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:11Z" - latency: 7.311641ms message: 'load-balancer-api-external: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:11Z" - latency: 6.092498ms message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:11Z" - latency: 8.083269ms message: 'load-balancer-api-external: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:11Z" - latency: 5.494085ms message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:11Z" - latency: 7.401939ms message: 'load-balancer-api-external: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:11Z" - latency: 4.812119ms message: 'load-balancer-api-external: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 8.26167ms message: 'load-balancer-api-external: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:12:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "20850" uid: 3018f411-dbd4-4db3-9c40-a019e47ba515 spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:04:11Z" message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.95679ms message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:11Z" - latency: 7.230926ms message: 'load-balancer-api-internal: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:11Z" - latency: 6.166065ms message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:11Z" - latency: 7.382111ms message: 'load-balancer-api-internal: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:11Z" - latency: 6.120701ms message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:11Z" - latency: 7.990476ms message: 'load-balancer-api-internal: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:11Z" - latency: 5.363183ms message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:11Z" - latency: 7.25731ms message: 'load-balancer-api-internal: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:11Z" - latency: 5.441768ms message: 'load-balancer-api-internal: tcp connection to a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 8.203496ms message: 'load-balancer-api-internal: resolved host name a8db5b969e950483188b6531afe0b5a5-bceca851381a2b43.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:12:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-network-check-target-ip-10-0-130-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "18734" uid: 08341475-e8f1-41ab-a0dd-1933261d956f spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:05:11Z" message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.556398ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 2.024889ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:11Z" - latency: 1.826916ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:11Z" - latency: 2.036314ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:11Z" - latency: 2.251863ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:11Z" - latency: 2.027603ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:11Z" - latency: 1.68158ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:11Z" - latency: 2.095713ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:11Z" - latency: 1.866699ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:04:11Z" - latency: 1.831969ms message: 'network-check-target-ip-10-0-130-202: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-network-check-target-ip-10-0-132-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "18736" uid: 8ecbf64f-8943-4294-8322-ea469ee0417c spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:05:11Z" message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.049194ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 2.1275ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:11Z" - latency: 2.356424ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:11Z" - latency: 2.296115ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:11Z" - latency: 2.405745ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:11Z" - latency: 2.235024ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:11Z" - latency: 2.139986ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:11Z" - latency: 2.210962ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:11Z" - latency: 2.169142ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:04:11Z" - latency: 2.090832ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-network-check-target-ip-10-0-141-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "18735" uid: df504662-6c47-481d-be77-977939bef7f1 spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:05:11Z" message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.219583ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 1.17791ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:11Z" - latency: 1.792783ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:11Z" - latency: 1.621924ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:11Z" - latency: 872.641µs message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:11Z" - latency: 1.557435ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:11Z" - latency: 868.282µs message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:11Z" - latency: 1.06108ms message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:11Z" - latency: 880.378µs message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:04:11Z" - latency: 814.859µs message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:03:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-209-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-209.ec2.internal uid: e5739347-6280-4c45-b7f8-c6d0090d710c resourceVersion: "20848" uid: 79ebdaed-930f-4804-bf94-b2262f09924f spec: sourcePod: network-check-source-8894fc9bd-b5c9q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T18:04:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.458µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:11Z" - latency: 2.090673ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:11Z" - latency: 828.248µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:11Z" - latency: 2.364711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:11Z" - latency: 949.632µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:11Z" - latency: 1.839614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:11Z" - latency: 827.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:11Z" - latency: 1.993457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:11Z" - latency: 904.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:11Z" - latency: 1.80235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:12:11Z" kind: List metadata: resourceVersion: ""