apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "47990" uid: e885c003-3a96-423b-8599-d01e2caf8f67 spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T20:45:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.257µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:06:45Z" - latency: 1.117591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:05:45Z" - latency: 970.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:04:45Z" - latency: 1.049845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:03:45Z" - latency: 1.016585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 1.162373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 1.121195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 1.127812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 1.042478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 1.143183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "41959" uid: fbc9df80-90b5-4da0-868a-46e0e14e680e spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:44:45Z" message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.31487ms message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 8.575647ms message: 'load-balancer-api-external: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:02:45Z" - latency: 4.739745ms message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 7.936242ms message: 'load-balancer-api-external: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:01:45Z" - latency: 4.185168ms message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 9.028558ms message: 'load-balancer-api-external: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:00:45Z" - latency: 4.648468ms message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 10.93077ms message: 'load-balancer-api-external: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:59:45Z" - latency: 4.7722ms message: 'load-balancer-api-external: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 7.668566ms message: 'load-balancer-api-external: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "41960" uid: 299de8f2-6438-4761-88c9-4f23e187993c spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:44:45Z" message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.326422ms message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 8.479446ms message: 'load-balancer-api-internal: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:02:45Z" - latency: 5.110243ms message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 7.985227ms message: 'load-balancer-api-internal: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:01:45Z" - latency: 5.505576ms message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 8.962727ms message: 'load-balancer-api-internal: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:00:45Z" - latency: 4.59361ms message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 11.022894ms message: 'load-balancer-api-internal: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:59:45Z" - latency: 4.811138ms message: 'load-balancer-api-internal: tcp connection to a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 7.634293ms message: 'load-balancer-api-internal: resolved host name a58899540cb3849c4a34cbcf3be4a2da-81326695ca9cc798.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T20:58:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-130-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "47987" uid: bf7a5985-9f18-417b-bcb7-5685844ac98b spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:45:45Z" message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.31µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:06:45Z" - latency: 1.205265ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:05:45Z" - latency: 1.040256ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:04:45Z" - latency: 1.098647ms message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:03:45Z" - latency: 888.627µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 752.136µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 934.604µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 831.495µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 822.64µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 805.589µs message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-137-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "47989" uid: 32ce5ded-2104-4d78-bbcb-bb36655fabf5 spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:45:45Z" message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.469194ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:06:45Z" - latency: 2.65258ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:05:45Z" - latency: 2.239573ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:04:45Z" - latency: 2.215842ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:03:45Z" - latency: 2.29282ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 2.22543ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 2.518987ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 2.310324ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 2.259059ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 2.04221ms message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-ip-10-0-139-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "47988" uid: a5a0d84e-4868-4605-a15f-01e4e2309dc5 spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:45:45Z" message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.064516ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:06:45Z" - latency: 2.19059ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:05:45Z" - latency: 1.783036ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:04:45Z" - latency: 2.042536ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:03:45Z" - latency: 1.993643ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 1.827802ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 1.901544ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 2.007706ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 1.915988ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 1.673452ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:57:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:38:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-119-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-119.ec2.internal uid: 6b714e3d-a8e3-4a63-840b-f7d787bca75c resourceVersion: "41958" uid: f8e36204-196c-4981-94a7-89c41e6e8c38 spec: sourcePod: network-check-source-7d88cb55d8-zk5pq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T20:44:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.767µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:02:45Z" - latency: 1.690048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:02:45Z" - latency: 963.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:01:45Z" - latency: 1.79161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:01:45Z" - latency: 1.074761ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:00:45Z" - latency: 2.019322ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:00:45Z" - latency: 799.372µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:59:45Z" - latency: 1.783619ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:59:45Z" - latency: 875.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T20:58:45Z" - latency: 1.669534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T20:58:45Z" kind: List metadata: resourceVersion: ""