apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "81794" uid: 9e50d391-d4c7-4d3a-93c1-bbb0d8f674ea spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-25T01:22:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 1.086511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 1.186013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:16:01Z" - latency: 682.882µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:15:01Z" - latency: 774.862µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:14:01Z" - latency: 800.257µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:13:01Z" - latency: 1.143454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:12:01Z" - latency: 802.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:11:01Z" - latency: 881.388µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:10:01Z" - latency: 1.087787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:09:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "88769" uid: 980b5fda-cfa7-4e13-a4c8-ea8ab22d47fe spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-25T01:21:01Z" message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.127594ms message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:21:01Z" - latency: 8.572549ms message: 'load-balancer-api-external: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:21:01Z" - latency: 5.772399ms message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:20:01Z" - latency: 7.779707ms message: 'load-balancer-api-external: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:20:01Z" - latency: 5.712575ms message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:19:01Z" - latency: 8.913102ms message: 'load-balancer-api-external: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:19:01Z" - latency: 6.506525ms message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 10.696608ms message: 'load-balancer-api-external: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:18:01Z" - latency: 4.877825ms message: 'load-balancer-api-external: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 8.44136ms message: 'load-balancer-api-external: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "88770" uid: 3699aa40-3319-43c4-bb29-844620e21582 spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-25T01:21:01Z" message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.875202ms message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:21:01Z" - latency: 8.607244ms message: 'load-balancer-api-internal: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:21:01Z" - latency: 5.801887ms message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:20:01Z" - latency: 7.813895ms message: 'load-balancer-api-internal: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:20:01Z" - latency: 5.804992ms message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:19:01Z" - latency: 8.936242ms message: 'load-balancer-api-internal: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:19:01Z" - latency: 6.553585ms message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 10.742507ms message: 'load-balancer-api-internal: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:18:01Z" - latency: 4.901377ms message: 'load-balancer-api-internal: tcp connection to acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 8.477876ms message: 'load-balancer-api-internal: resolved host name acc470b471c204eb7b35f24d8e4a5c1a-9386e4a8660badd2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:17:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-network-check-target-ip-10-0-130-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "81793" uid: 2a3b4fcb-3e04-4981-a21d-f6e9b8157981 spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:22:01Z" message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.685436ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 2.003783ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 1.896398ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:16:01Z" - latency: 1.520666ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:15:01Z" - latency: 1.657824ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:14:01Z" - latency: 1.816467ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:13:01Z" - latency: 1.553014ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:12:01Z" - latency: 1.644096ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:11:01Z" - latency: 1.761486ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:10:01Z" - latency: 1.631357ms message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:09:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-network-check-target-ip-10-0-134-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "81791" uid: 1ef25411-5e4b-4855-a898-23e57f171430 spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:22:01Z" message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.686µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 826.723µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 775.441µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:16:01Z" - latency: 694.519µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:15:01Z" - latency: 1.175303ms message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:14:01Z" - latency: 747.637µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:13:01Z" - latency: 1.113571ms message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:12:01Z" - latency: 753.551µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:11:01Z" - latency: 811.161µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:10:01Z" - latency: 794.411µs message: 'network-check-target-ip-10-0-134-238: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:09:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-network-check-target-ip-10-0-135-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "81792" uid: 597c92a2-fcbd-4892-abca-8ac467aabd28 spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:22:01Z" message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.950399ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 2.11784ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 1.906893ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:16:01Z" - latency: 1.865892ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:15:01Z" - latency: 1.920113ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:14:01Z" - latency: 1.921165ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:13:01Z" - latency: 1.914429ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:12:01Z" - latency: 2.084937ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:11:01Z" - latency: 1.916499ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:10:01Z" - latency: 2.016079ms message: 'network-check-target-ip-10-0-135-43: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:09:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:15:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-238-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-238.ec2.internal uid: 84457f0c-3077-4c95-9140-7a16dace80f8 resourceVersion: "88768" uid: c2c7514a-0ea0-4abc-9089-fab6515ed1cb spec: sourcePod: network-check-source-7d88cb55d8-bv82n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-25T01:21:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 829.169µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:21:01Z" - latency: 1.740698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:21:01Z" - latency: 860.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:20:01Z" - latency: 2.016576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:20:01Z" - latency: 891.725µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:19:01Z" - latency: 1.613938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:19:01Z" - latency: 1.024527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:18:01Z" - latency: 1.813278ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:18:01Z" - latency: 959.207µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:17:01Z" - latency: 1.719294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:17:01Z" kind: List metadata: resourceVersion: ""