apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "19824" uid: 9561a534-7637-4017-974f-5f8fe898e403 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-07T10:19:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.318µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 759.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 864.444µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:31:59Z" - latency: 865.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:30:59Z" - latency: 1.02351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:29:59Z" - latency: 1.094725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:28:59Z" - latency: 873.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:27:59Z" - latency: 1.099493ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:26:59Z" - latency: 926.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:25:59Z" - latency: 882.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "21093" uid: 21f598fc-24b7-420c-9e56-2a609ab75821 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T10:18:59Z" message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.579742ms message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:36:59Z" - latency: 8.082935ms message: 'load-balancer-api-external: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:36:59Z" - latency: 3.497443ms message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:35:59Z" - latency: 7.424889ms message: 'load-balancer-api-external: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:35:59Z" - latency: 4.531957ms message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:34:59Z" - latency: 8.01797ms message: 'load-balancer-api-external: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:34:59Z" - latency: 4.089631ms message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 7.674554ms message: 'load-balancer-api-external: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:33:59Z" - latency: 3.622452ms message: 'load-balancer-api-external: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 8.942462ms message: 'load-balancer-api-external: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:32:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "21094" uid: 80624939-5a63-4500-a5d5-5f658ef58466 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T10:18:59Z" message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.559947ms message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:36:59Z" - latency: 8.177975ms message: 'load-balancer-api-internal: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:36:59Z" - latency: 3.457211ms message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:35:59Z" - latency: 7.478845ms message: 'load-balancer-api-internal: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:35:59Z" - latency: 4.075989ms message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:34:59Z" - latency: 8.110414ms message: 'load-balancer-api-internal: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:34:59Z" - latency: 4.61326ms message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 7.760186ms message: 'load-balancer-api-internal: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:33:59Z" - latency: 3.876636ms message: 'load-balancer-api-internal: tcp connection to ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 8.998526ms message: 'load-balancer-api-internal: resolved host name ae9de06322f5f457c9bc051133c9dfde-30a6ff9c04a02628.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T10:32:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-network-check-target-ip-10-0-131-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "19821" uid: 92e3f9b6-8b37-4520-ace4-475a4efc7ca0 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T10:19:59Z" message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 819.175µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 1.498465ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 856.716µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:31:59Z" - latency: 791.277µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:30:59Z" - latency: 885.571µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:29:59Z" - latency: 704.33µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:28:59Z" - latency: 776.815µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:27:59Z" - latency: 858.922µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:26:59Z" - latency: 825.579µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:25:59Z" - latency: 689.309µs message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-network-check-target-ip-10-0-140-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "19822" uid: 698365f6-ed7d-479b-a8c6-3954c66cbffc spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-07T10:19:59Z" message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.877619ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 2.159019ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 1.983286ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:31:59Z" - latency: 2.363044ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:30:59Z" - latency: 2.002204ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:29:59Z" - latency: 1.934029ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:28:59Z" - latency: 1.822024ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:27:59Z" - latency: 2.019058ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:26:59Z" - latency: 6.56441ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:25:59Z" - latency: 1.792718ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-network-check-target-ip-10-0-141-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "19823" uid: 4d24a9dc-68e5-408a-a099-83a1e7d20e54 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T10:19:59Z" message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.172477ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 2.192097ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 2.235964ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:31:59Z" - latency: 1.954545ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:30:59Z" - latency: 2.273151ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:29:59Z" - latency: 1.893406ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:28:59Z" - latency: 1.980187ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:27:59Z" - latency: 2.181255ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:26:59Z" - latency: 2.196322ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:25:59Z" - latency: 2.069724ms message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:24:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T10:12:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-125.ec2.internal uid: a770dbff-0285-49d4-b28d-b6f0df0b89e1 resourceVersion: "21092" uid: 2e3ce999-89b3-43e3-ac3a-dabee6daf8c9 spec: sourcePod: network-check-source-685456655f-rqr9r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-07T10:18:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 796.648µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:36:59Z" - latency: 1.644132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T10:36:59Z" - latency: 805.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:35:59Z" - latency: 1.613213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T10:35:59Z" - latency: 1.004907ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:34:59Z" - latency: 1.624827ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T10:34:59Z" - latency: 871.212µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:33:59Z" - latency: 1.540374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T10:33:59Z" - latency: 1.094054ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T10:32:59Z" - latency: 2.175334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T10:32:59Z" kind: List metadata: resourceVersion: ""