apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "19995" uid: 64bf0b16-d165-4e22-aec9-d10b88d3b4f0 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T08:13:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 1.395294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 1.303357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:25:38Z" - latency: 879.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:24:38Z" - latency: 925.962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:23:38Z" - latency: 903.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:22:38Z" - latency: 861.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:21:38Z" - latency: 1.276642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:20:38Z" - latency: 1.02472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:19:38Z" - latency: 797.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "21186" uid: f431fe59-9809-4c03-9d12-070ffa2436b4 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T08:12:38Z" message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.863192ms message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:38Z" - latency: 7.330282ms message: 'load-balancer-api-external: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:30:38Z" - latency: 5.759251ms message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:38Z" - latency: 7.72964ms message: 'load-balancer-api-external: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:29:38Z" - latency: 5.626262ms message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:38Z" - latency: 7.769366ms message: 'load-balancer-api-external: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:28:38Z" - latency: 3.399421ms message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 9.477205ms message: 'load-balancer-api-external: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:27:38Z" - latency: 5.641474ms message: 'load-balancer-api-external: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 7.786993ms message: 'load-balancer-api-external: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "21187" uid: b7c91e00-79b2-4588-be0c-9c521f8c828d spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T08:12:38Z" message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.853144ms message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:38Z" - latency: 7.382308ms message: 'load-balancer-api-internal: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:30:38Z" - latency: 5.723961ms message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:38Z" - latency: 7.782884ms message: 'load-balancer-api-internal: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:29:38Z" - latency: 29.625027ms message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:38Z" - latency: 7.825291ms message: 'load-balancer-api-internal: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:28:38Z" - latency: 3.363079ms message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 9.548872ms message: 'load-balancer-api-internal: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:27:38Z" - latency: 5.661624ms message: 'load-balancer-api-internal: tcp connection to a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 7.822814ms message: 'load-balancer-api-internal: resolved host name a8a3ff9d453bb4aa0954b8e279ed2a8b-a0f0d68efdfdae5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T08:26:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-136-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "19992" uid: 0c34d89d-7550-4f98-b3e2-1b99782ca892 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:13:38Z" message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164922ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 1.912324ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 2.602074ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:25:38Z" - latency: 2.186101ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:24:38Z" - latency: 2.093135ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:23:38Z" - latency: 2.040102ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:22:38Z" - latency: 2.315898ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:21:38Z" - latency: 2.223777ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:20:38Z" - latency: 2.200322ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:19:38Z" - latency: 2.08512ms message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-139-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "19994" uid: 120a77b5-d86b-4d8d-af7c-ab6a9588dfd1 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:13:38Z" message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.655µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 837.679µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 1.040405ms message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:25:38Z" - latency: 807.71µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:24:38Z" - latency: 886.602µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:23:38Z" - latency: 833.159µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:22:38Z" - latency: 925.924µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:21:38Z" - latency: 918.864µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:20:38Z" - latency: 882.529µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:19:38Z" - latency: 992.538µs message: 'network-check-target-ip-10-0-139-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-ip-10-0-141-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "19993" uid: 847d05b2-d9d4-4d37-8f18-9c7d069d2f42 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T08:13:38Z" message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141132ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 2.296276ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 2.163615ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:25:38Z" - latency: 2.10472ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:24:38Z" - latency: 2.037005ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:23:38Z" - latency: 1.885733ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:22:38Z" - latency: 2.158907ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:21:38Z" - latency: 2.086433ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:20:38Z" - latency: 2.117375ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:19:38Z" - latency: 2.110872ms message: 'network-check-target-ip-10-0-141-246: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T08:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-133.ec2.internal uid: 33504bef-74c5-4f02-a0f4-c98ec02df6b2 resourceVersion: "21185" uid: 20e30808-dc5b-4c32-969d-55c05bb5ec05 spec: sourcePod: network-check-source-7f44b6dd87-b4xhl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T08:12:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.017248ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:30:38Z" - latency: 1.605849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:30:38Z" - latency: 815.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:29:38Z" - latency: 1.671587ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:29:38Z" - latency: 835.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:28:38Z" - latency: 1.701261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:28:38Z" - latency: 835.178µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:27:38Z" - latency: 2.308806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:27:38Z" - latency: 922.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T08:26:38Z" - latency: 1.653568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T08:26:38Z" kind: List metadata: resourceVersion: ""