apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "53589" uid: 5b98af64-33f7-4825-b4d2-2bb92aab4da6 spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:13:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:41:28Z" - latency: 903.864µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:40:28Z" - latency: 1.144284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:39:28Z" - latency: 1.359578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:38:28Z" - latency: 970.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:37:28Z" - latency: 1.198994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 1.824923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 1.46564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 885.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 1.318699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "48785" uid: 41651bb1-72c5-4c1c-9606-7d520dbaf462 spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:12:28Z" message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.046634ms message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 9.330201ms message: 'load-balancer-api-external: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:36:28Z" - latency: 4.483312ms message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 7.880844ms message: 'load-balancer-api-external: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:35:28Z" - latency: 3.973719ms message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 9.137643ms message: 'load-balancer-api-external: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:34:28Z" - latency: 5.64996ms message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 9.722909ms message: 'load-balancer-api-external: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:33:28Z" - latency: 5.469565ms message: 'load-balancer-api-external: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - latency: 9.565004ms message: 'load-balancer-api-external: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "48784" uid: 27bf7cb7-3df8-412f-964a-de8e24d488a9 spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T16:12:28Z" message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.040024ms message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 9.369862ms message: 'load-balancer-api-internal: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:36:28Z" - latency: 3.786424ms message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 7.915432ms message: 'load-balancer-api-internal: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:35:28Z" - latency: 6.147157ms message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 9.182376ms message: 'load-balancer-api-internal: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:34:28Z" - latency: 5.671141ms message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 9.783321ms message: 'load-balancer-api-internal: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:33:28Z" - latency: 5.483837ms message: 'load-balancer-api-internal: tcp connection to acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - latency: 9.5745ms message: 'load-balancer-api-internal: resolved host name acd805143583846ae9c151e4dc939c8c-506ff3f14f5c7e8d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-network-check-target-ip-10-0-136-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "53588" uid: c5ed737f-994c-40c3-ab21-f11c76fb017b spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:13:28Z" message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.000669ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:41:28Z" - latency: 2.065807ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:40:28Z" - latency: 2.362423ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:39:28Z" - latency: 2.433463ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:38:28Z" - latency: 2.302064ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:37:28Z" - latency: 1.986197ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 2.50708ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 2.220251ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 2.372969ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 2.266421ms message: 'network-check-target-ip-10-0-136-114: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-network-check-target-ip-10-0-138-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "53587" uid: 45b121ca-6698-4bfe-b632-ff6aac4d87bf spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:13:28Z" message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.865408ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:41:28Z" - latency: 1.743502ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:40:28Z" - latency: 2.027981ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:39:28Z" - latency: 2.018427ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:38:28Z" - latency: 2.25323ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:37:28Z" - latency: 2.273393ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 1.807446ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 2.147314ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 1.769917ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 1.939461ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-network-check-target-ip-10-0-141-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "53586" uid: 72d44ca6-3ae9-44bf-a9a6-5ce80a9ed845 spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:13:28Z" message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.215665ms message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:41:28Z" - latency: 1.161229ms message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:40:28Z" - latency: 810.26µs message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:39:28Z" - latency: 1.006594ms message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:38:28Z" - latency: 878.601µs message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:37:28Z" - latency: 1.201003ms message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 914.463µs message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 1.411066ms message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 929.839µs message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 825.711µs message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T16:06:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-121.ec2.internal uid: ca40e87f-c36b-45aa-a335-fe66f27f8cfc resourceVersion: "48782" uid: 99a88276-928a-49bc-88a8-c357a2738f8f spec: sourcePod: network-check-source-989f8b8dc-j86w8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T16:12:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 721.923µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:36:28Z" - latency: 1.743391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:36:28Z" - latency: 836.871µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:35:28Z" - latency: 2.239793ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:35:28Z" - latency: 981.128µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:34:28Z" - latency: 2.246646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:34:28Z" - latency: 822.192µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:33:28Z" - latency: 1.81772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:33:28Z" - latency: 1.001346ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:32:28Z" - latency: 1.923867ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:32:28Z" kind: List metadata: resourceVersion: ""