apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "66996" uid: eae47fc0-4967-4489-9b18-9b6e314ca7dc spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T18:59:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 1.018239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 948.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 1.22808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 1.141416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:23:02Z" - latency: 1.242314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:22:02Z" - latency: 1.157294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:21:02Z" - latency: 1.093851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:20:02Z" - latency: 2.006799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:19:02Z" - latency: 1.005446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "68022" uid: 79285212-195f-4eba-8d84-669a6f7787bb spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T18:58:02Z" message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.800915ms message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:28:02Z" - latency: 9.872058ms message: 'load-balancer-api-external: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:28:02Z" - latency: 4.581375ms message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 8.285601ms message: 'load-balancer-api-external: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:27:02Z" - latency: 4.754784ms message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 11.636612ms message: 'load-balancer-api-external: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:26:02Z" - latency: 4.341808ms message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 7.186386ms message: 'load-balancer-api-external: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:25:02Z" - latency: 5.541869ms message: 'load-balancer-api-external: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 8.365042ms message: 'load-balancer-api-external: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:24:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "68021" uid: 43c9dc4f-0373-4390-8314-90767cecce83 spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T18:58:02Z" message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.752611ms message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:28:02Z" - latency: 9.912314ms message: 'load-balancer-api-internal: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:28:02Z" - latency: 4.562781ms message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 8.254331ms message: 'load-balancer-api-internal: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:27:02Z" - latency: 4.720914ms message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 11.692586ms message: 'load-balancer-api-internal: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:26:02Z" - latency: 4.35743ms message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 7.142811ms message: 'load-balancer-api-internal: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:25:02Z" - latency: 5.577153ms message: 'load-balancer-api-internal: tcp connection to a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 8.44063ms message: 'load-balancer-api-internal: resolved host name a72ea4fe6d2ee4b01b3d28033d4a99ad-edba18b97e307f81.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T19:24:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-network-check-target-ip-10-0-134-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "66992" uid: 52ca0c63-5e7e-4799-9592-ab5f6dcc82be spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:59:02Z" message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.417182ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 2.377308ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 2.292111ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 2.216355ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 2.371183ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:23:02Z" - latency: 2.479763ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:22:02Z" - latency: 2.414858ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:21:02Z" - latency: 2.502576ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:20:02Z" - latency: 3.029055ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:19:02Z" - latency: 2.498346ms message: 'network-check-target-ip-10-0-134-189: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-network-check-target-ip-10-0-134-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "66993" uid: 910d94dd-3ef7-44f5-817f-7788fc644fad spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:59:02Z" message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.518067ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 1.116879ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 988.967µs message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 1.260904ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 1.084457ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:23:02Z" - latency: 1.588028ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:22:02Z" - latency: 983.876µs message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:21:02Z" - latency: 1.149558ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:20:02Z" - latency: 1.251965ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:19:02Z" - latency: 1.054584ms message: 'network-check-target-ip-10-0-134-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-network-check-target-ip-10-0-143-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "66994" uid: b31ce064-2536-4b13-8e25-bad1185befbe spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T18:59:02Z" message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.235231ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 2.042237ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 1.504282ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 2.042047ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 2.016646ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:23:02Z" - latency: 2.017896ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:22:02Z" - latency: 3.051389ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:21:02Z" - latency: 2.151866ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:20:02Z" - latency: 2.476902ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:19:02Z" - latency: 2.269846ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T18:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-233-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-233.ec2.internal uid: 2e76d6a0-9061-4033-b723-561904998c48 resourceVersion: "68020" uid: 9a513036-404f-47c8-913b-d2c0949a8355 spec: sourcePod: network-check-source-6f8b768455-9rm2z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T18:58:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 921.948µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:28:02Z" - latency: 2.016828ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T19:28:02Z" - latency: 1.012188ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:27:02Z" - latency: 1.73759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T19:27:02Z" - latency: 1.341845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:26:02Z" - latency: 1.873513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T19:26:02Z" - latency: 1.004541ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:25:02Z" - latency: 1.96972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T19:25:02Z" - latency: 860.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T19:24:02Z" - latency: 2.945624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T19:24:02Z" kind: List metadata: resourceVersion: ""