apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "21621" uid: da77585d-dd9b-42ec-9a42-eeaf1544502b spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T10:12: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.026411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 1.433759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 783.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 1.045962ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:30:25Z" - latency: 1.022666ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:29:25Z" - latency: 938.361µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:28:25Z" - latency: 1.025807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:27:25Z" - latency: 1.325033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:26:25Z" - latency: 1.219638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:25:25Z" - latency: 993.158µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:24:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "22567" uid: 82e7c0b0-178b-479e-9ee5-8ba1f80e86a0 spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T10:11:25Z" message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.157841ms message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:35:25Z" - latency: 9.672776ms message: 'load-balancer-api-external: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:35:25Z" - latency: 3.911631ms message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:34:25Z" - latency: 7.147031ms message: 'load-balancer-api-external: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:34:25Z" - latency: 4.251618ms message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 8.202692ms message: 'load-balancer-api-external: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:33:25Z" - latency: 5.781166ms message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 9.671298ms message: 'load-balancer-api-external: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:32:25Z" - latency: 6.227581ms message: 'load-balancer-api-external: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 7.640773ms message: 'load-balancer-api-external: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:31:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "22566" uid: 88e158c3-3410-43b6-9a30-5222df71928b spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T10:11:25Z" message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.560988ms message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:35:25Z" - latency: 9.76634ms message: 'load-balancer-api-internal: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:35:25Z" - latency: 3.821174ms message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:34:25Z" - latency: 7.172845ms message: 'load-balancer-api-internal: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:34:25Z" - latency: 4.500443ms message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 8.09326ms message: 'load-balancer-api-internal: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:33:25Z" - latency: 5.475229ms message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 9.771712ms message: 'load-balancer-api-internal: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:32:25Z" - latency: 6.090108ms message: 'load-balancer-api-internal: tcp connection to a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 7.558405ms message: 'load-balancer-api-internal: resolved host name a1d67bc70229748519b19bda412858fd-4c86189ea09433c0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T10:31:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-137-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "21620" uid: 6e083718-4548-447e-8037-73344e003922 spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T10:12:25Z" message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.216449ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 2.391798ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 2.46327ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 2.059008ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:30:25Z" - latency: 2.229784ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:29:25Z" - latency: 2.252202ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:28:25Z" - latency: 2.692962ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:27:25Z" - latency: 2.373706ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:26:25Z" - latency: 3.232489ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:25:25Z" - latency: 3.462066ms message: 'network-check-target-ip-10-0-137-106: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:24:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-138-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "21619" uid: 239e0339-86e7-458e-ba96-f6597e96dbe5 spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T10:12:25Z" message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.33179ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 2.595556ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 1.86703ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 2.370468ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:30:25Z" - latency: 2.4836ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:29:25Z" - latency: 2.736209ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:28:25Z" - latency: 2.477805ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:27:25Z" - latency: 2.52172ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:26:25Z" - latency: 1.978474ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:25:25Z" - latency: 1.856396ms message: 'network-check-target-ip-10-0-138-148: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:24:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-140-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "21618" uid: 439cabbe-c7cd-450b-8535-4712b2919a32 spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T10:12:25Z" message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.418957ms message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 989.356µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 973.173µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 1.027127ms message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:30:25Z" - latency: 940.698µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:29:25Z" - latency: 1.171931ms message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:28:25Z" - latency: 916.754µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:27:25Z" - latency: 1.835731ms message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:26:25Z" - latency: 835.846µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:25:25Z" - latency: 877.989µs message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:24:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T10:05:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-95.ec2.internal uid: 8d4f64b9-313b-422b-9883-f5e39d2e9d2e resourceVersion: "22565" uid: 990881e3-1b21-45f6-9677-bd5d5291418f spec: sourcePod: network-check-source-8894fc9bd-4dcjg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T10:11:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.119864ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:35:25Z" - latency: 2.304429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T10:35:25Z" - latency: 794.653µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:34:25Z" - latency: 1.735381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T10:34:25Z" - latency: 1.121042ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:33:25Z" - latency: 2.043469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T10:33:25Z" - latency: 1.109594ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:32:25Z" - latency: 2.245156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T10:32:25Z" - latency: 897.602µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T10:31:25Z" - latency: 1.866716ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T10:31:25Z" kind: List metadata: resourceVersion: ""