apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63223" uid: cbc81063-9ede-4371-a91c-f1992dfcb73d spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:40:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 1.213942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 1.312411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 1.233802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 1.689617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 969.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:10:27Z" - latency: 1.92564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:09:27Z" - latency: 1.138211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:08:27Z" - latency: 1.155564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:07:27Z" - latency: 1.513421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:06:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63225" uid: 2588019b-71bb-4048-9b6b-dcc7704dd85e spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:39:27Z" message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.250363ms message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 8.547989ms message: 'load-balancer-api-external: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:15:27Z" - latency: 3.562925ms message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 7.77387ms message: 'load-balancer-api-external: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:14:27Z" - latency: 5.191014ms message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 7.637889ms message: 'load-balancer-api-external: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:13:27Z" - latency: 3.983871ms message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 7.451876ms message: 'load-balancer-api-external: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:12:27Z" - latency: 5.252766ms message: 'load-balancer-api-external: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 7.013113ms message: 'load-balancer-api-external: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63224" uid: 2b92291b-8166-49c3-a691-a42d242e1763 spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:39:27Z" message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.448585ms message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 8.675044ms message: 'load-balancer-api-internal: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:15:27Z" - latency: 3.585005ms message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 7.970593ms message: 'load-balancer-api-internal: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:14:27Z" - latency: 5.228016ms message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 7.848509ms message: 'load-balancer-api-internal: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:13:27Z" - latency: 3.90702ms message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 7.405927ms message: 'load-balancer-api-internal: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:12:27Z" - latency: 5.264292ms message: 'load-balancer-api-internal: tcp connection to aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 7.092249ms message: 'load-balancer-api-internal: resolved host name aef6a4f4dd3874f6c8d1751cc0e6bdb1-f20db72aed36866f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:11:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-network-check-target-ip-10-0-130-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63221" uid: d7f6a2b6-c0d2-4715-8df8-31fca11f8165 spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:40:27Z" message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.243873ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 2.177416ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 1.98569ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 1.849206ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 2.096578ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 2.07586ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:10:27Z" - latency: 2.843097ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:09:27Z" - latency: 2.076676ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:08:27Z" - latency: 2.082901ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:07:27Z" - latency: 2.273945ms message: 'network-check-target-ip-10-0-130-51: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:06:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-network-check-target-ip-10-0-134-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63220" uid: b41360eb-1efc-4a64-933d-7d4b27082b98 spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:40:27Z" message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.208013ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 1.946277ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 1.749909ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 2.264943ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 2.393299ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 2.321362ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:10:27Z" - latency: 2.946183ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:09:27Z" - latency: 2.252976ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:08:27Z" - latency: 2.472008ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:07:27Z" - latency: 2.500662ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:06:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-network-check-target-ip-10-0-136-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63219" uid: cfbb9888-876c-497f-a80b-2195e0db4f15 spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:40:27Z" message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.155566ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 1.283271ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 1.752746ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 930.928µs message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 1.236758ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 1.0561ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:10:27Z" - latency: 2.003755ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:09:27Z" - latency: 1.235336ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:08:27Z" - latency: 1.097388ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:07:27Z" - latency: 1.957639ms message: 'network-check-target-ip-10-0-136-229: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:06:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:33:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-229-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-229.ec2.internal uid: 672e10ea-80ed-47d7-98e8-fe55836236de resourceVersion: "63222" uid: 24546552-b9f5-4779-8d5e-9866278e9bd9 spec: sourcePod: network-check-source-869dcfcdcd-h9pdc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:39:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:27Z" - latency: 2.186466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:15:27Z" - latency: 897.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:27Z" - latency: 1.958071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:14:27Z" - latency: 823.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:27Z" - latency: 2.646709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:13:27Z" - latency: 1.00699ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:27Z" - latency: 2.606395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:12:27Z" - latency: 1.303251ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:27Z" - latency: 1.974095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:11:27Z" kind: List metadata: resourceVersion: ""