apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "22975" uid: a6bcacf7-ccf4-4039-af62-07b0ab7d890d spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T19:16:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:30:17Z" - latency: 995.236µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:29:17Z" - latency: 754.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:28:17Z" - latency: 941.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 923.762µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 856.605µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 1.272775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 1.298674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 988.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:22:17Z" - latency: 869.307µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:21:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "21489" uid: 2fe5fcfd-9065-437c-842a-551604dadbe5 spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T19:15:17Z" message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.472507ms message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 7.681742ms message: 'load-balancer-api-external: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:27:17Z" - latency: 5.144694ms message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 10.454945ms message: 'load-balancer-api-external: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:26:17Z" - latency: 5.329682ms message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 8.609818ms message: 'load-balancer-api-external: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:25:17Z" - latency: 6.101302ms message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 7.492738ms message: 'load-balancer-api-external: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:24:17Z" - latency: 5.147233ms message: 'load-balancer-api-external: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 9.128182ms message: 'load-balancer-api-external: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:23:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "21488" uid: 6f517326-46a6-4eb7-8a8e-22e6afa4f1c8 spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T19:15:17Z" message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.854124ms message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 7.739338ms message: 'load-balancer-api-internal: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:27:17Z" - latency: 4.782865ms message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 10.374995ms message: 'load-balancer-api-internal: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:26:17Z" - latency: 5.358249ms message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 8.510907ms message: 'load-balancer-api-internal: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:25:17Z" - latency: 6.145942ms message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 7.427193ms message: 'load-balancer-api-internal: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:24:17Z" - latency: 5.696298ms message: 'load-balancer-api-internal: tcp connection to ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 9.061182ms message: 'load-balancer-api-internal: resolved host name ae7353d864ddf49c6aa857eb5e0df925-f16a13416df37e9d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:23:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-131-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "22973" uid: 1ef37063-6a25-4d06-8026-287fb15949a2 spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:17Z" message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.087µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:30:17Z" - latency: 855.252µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:29:17Z" - latency: 854.344µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:28:17Z" - latency: 759.265µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 821.165µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 788.812µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 965.993µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 1.69296ms message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 984.665µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:22:17Z" - latency: 861.382µs message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:21:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-138-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "22974" uid: 76509200-85f5-4747-bc68-1ad7864dd48a spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:17Z" message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.655177ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:30:17Z" - latency: 1.713604ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:29:17Z" - latency: 1.517828ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:28:17Z" - latency: 2.00689ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 1.687326ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 1.799662ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 1.693256ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 1.911051ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 1.793241ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:22:17Z" - latency: 1.820798ms message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:21:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-140-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "22972" uid: d7a6bfa0-cbf4-4968-9c4c-f95812ba3f19 spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:17Z" message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.306054ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:30:17Z" - latency: 2.239174ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:29:17Z" - latency: 2.64082ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:28:17Z" - latency: 2.283689ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 2.10828ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 2.264543ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 2.196405ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 2.627751ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 2.428599ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:22:17Z" - latency: 2.31391ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:21:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-232-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-232.ec2.internal uid: 9c4fb8ea-d666-495a-ad01-92fde2585cd6 resourceVersion: "21486" uid: 2a20a464-72c1-40b2-b8a1-8e2e3babb266 spec: sourcePod: network-check-source-7cbc45fddc-h5bj4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T19:15:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 744.163µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:27:17Z" - latency: 1.58024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:27:17Z" - latency: 862.129µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:26:17Z" - latency: 1.918457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:26:17Z" - latency: 814.601µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:25:17Z" - latency: 2.546245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:25:17Z" - latency: 849.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:24:17Z" - latency: 1.675853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:24:17Z" - latency: 1.027647ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:23:17Z" - latency: 2.441017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:23:17Z" kind: List metadata: resourceVersion: ""