apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "85595" uid: b31a8975-08e7-4387-ae4c-93fd407b5009 spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T21:44:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.185673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:05Z" - latency: 1.595584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 1.274169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 1.015053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 972.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 1.032399ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 1.099856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:20:05Z" - latency: 1.117689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:19:05Z" - latency: 1.087906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:18:05Z" - latency: 816.345µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "83328" uid: aa1e0437-926c-457e-8a0a-e6fe0ed2d936 spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:43:05Z" message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.875626ms message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 7.405358ms message: 'load-balancer-api-external: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:25:05Z" - latency: 5.868631ms message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 6.919615ms message: 'load-balancer-api-external: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:24:05Z" - latency: 5.473058ms message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 7.808719ms message: 'load-balancer-api-external: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:23:05Z" - latency: 4.530124ms message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 7.118213ms message: 'load-balancer-api-external: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:22:05Z" - latency: 4.620641ms message: 'load-balancer-api-external: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 9.13701ms message: 'load-balancer-api-external: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:21:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "83327" uid: d3d0e611-066d-4258-a372-bc6f3b215324 spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:43:05Z" message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.841839ms message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 7.451401ms message: 'load-balancer-api-internal: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:25:05Z" - latency: 3.529579ms message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 6.885557ms message: 'load-balancer-api-internal: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:24:05Z" - latency: 5.505302ms message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 7.756487ms message: 'load-balancer-api-internal: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:23:05Z" - latency: 4.712764ms message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 7.035494ms message: 'load-balancer-api-internal: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:22:05Z" - latency: 3.361763ms message: 'load-balancer-api-internal: tcp connection to a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 9.18797ms message: 'load-balancer-api-internal: resolved host name a1975e2ca7f6c41d999b9a439c0ec849-0e8d6d289eca585a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:21:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T22:05:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-network-check-target-ip-10-0-132-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "86835" uid: abac6d2f-f712-4ced-a77a-d642a3bba9a1 spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T22:12:40Z" message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 948.269µs message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:40Z" - latency: 1.152284ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:40Z" - latency: 1.155862ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:40Z" - latency: 1.112754ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:40Z" - latency: 1.17723ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:40Z" - latency: 1.179516ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:40Z" - latency: 1.069463ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:20:40Z" - latency: 1.112421ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:19:40Z" - latency: 1.118359ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:18:40Z" - latency: 1.130583ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-network-check-target-ip-10-0-133-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "85593" uid: 3c56a5be-aafb-4a98-b1cd-7b818a494c5d spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:44:05Z" message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.631659ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:05Z" - latency: 2.29595ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 2.19891ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 2.243946ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 2.422624ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 1.863605ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 2.439641ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:20:05Z" - latency: 2.180302ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:19:05Z" - latency: 2.467439ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:18:05Z" - latency: 2.138203ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-network-check-target-ip-10-0-136-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "85594" uid: 72e4b052-b066-4ef8-bd91-5203b4b7c0d5 spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:44:05Z" message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.415463ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:05Z" - latency: 2.217425ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 2.408976ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 2.154355ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 1.805728ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 2.156585ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 2.266178ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:20:05Z" - latency: 2.086611ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:19:05Z" - latency: 2.256648ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:18:05Z" - latency: 2.117363ms message: 'network-check-target-ip-10-0-136-223: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:17:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-161.ec2.internal uid: 87146010-4217-41af-8c16-8b05f2ce2523 resourceVersion: "83326" uid: 10470277-b584-48bd-b407-4a56c30f015a spec: sourcePod: network-check-source-7d88cb55d8-qxnvt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T21:43:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.162083ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:05Z" - latency: 1.88238ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:25:05Z" - latency: 1.349627ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:05Z" - latency: 1.967279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:24:05Z" - latency: 1.319931ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:23:05Z" - latency: 1.600708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:23:05Z" - latency: 1.150946ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:22:05Z" - latency: 1.788483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:22:05Z" - latency: 907.338µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:21:05Z" - latency: 1.749175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:21:05Z" kind: List metadata: resourceVersion: ""