apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "54757" uid: 789d2c74-6111-4b05-baac-4818e90448c9 spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T12:53:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 1.062764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 886.726µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 1.263289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - latency: 875.995µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:17:40Z" - latency: 1.054791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 929.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 983.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 1.380121ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 1.131063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "49865" uid: 2dda8e79-f985-44d1-8127-5436ee425f71 spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T12:52:40Z" message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.186277ms message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 7.041076ms message: 'load-balancer-api-external: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:16:40Z" - latency: 6.237826ms message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 7.166329ms message: 'load-balancer-api-external: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:15:40Z" - latency: 4.761061ms message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 7.28299ms message: 'load-balancer-api-external: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:14:40Z" - latency: 3.980057ms message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 7.20556ms message: 'load-balancer-api-external: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:13:40Z" - latency: 4.202558ms message: 'load-balancer-api-external: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - latency: 8.289036ms message: 'load-balancer-api-external: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "49866" uid: eb971009-8732-4ecc-94df-5f57edfb17bb spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T12:52:40Z" message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.18729ms message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 6.976687ms message: 'load-balancer-api-internal: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:16:40Z" - latency: 4.325578ms message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 7.089632ms message: 'load-balancer-api-internal: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:15:40Z" - latency: 4.746302ms message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 7.246387ms message: 'load-balancer-api-internal: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:14:40Z" - latency: 3.981355ms message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 7.161369ms message: 'load-balancer-api-internal: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:13:40Z" - latency: 4.425123ms message: 'load-balancer-api-internal: tcp connection to a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - latency: 8.236508ms message: 'load-balancer-api-internal: resolved host name a43ca4eed76da4b158478421d58c2603-c3e10de6f3383634.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-network-check-target-ip-10-0-132-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "54754" uid: 7b0d64eb-a803-41fb-93bb-6e6add602df8 spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:53:40Z" message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.231375ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 2.469915ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 2.431351ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 2.305884ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - latency: 2.501707ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:17:40Z" - latency: 2.448261ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 2.218192ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 2.361429ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 2.286782ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 2.28609ms message: 'network-check-target-ip-10-0-132-141: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-network-check-target-ip-10-0-135-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "54755" uid: 209475b1-1221-4b88-9d03-86a1b91be714 spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:53:40Z" message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.123362ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 2.399671ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 2.408034ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 2.585327ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - latency: 2.551472ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:17:40Z" - latency: 2.414931ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 2.302639ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 2.510848ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 2.131325ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 2.661852ms message: 'network-check-target-ip-10-0-135-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-network-check-target-ip-10-0-141-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "54753" uid: 87546c0e-71a9-4ed5-8587-3c36bb93e2fc spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T12:53:40Z" message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005077ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:21:40Z" - latency: 1.413883ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:20:40Z" - latency: 881.495µs message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:19:40Z" - latency: 1.205891ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:18:40Z" - latency: 1.210641ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:17:40Z" - latency: 1.064578ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 974.793µs message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 1.027054ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 1.803282ms message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 895.103µs message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T12:46:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-76-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-76.ec2.internal uid: 32d66bc6-9df6-464e-83c0-2c6d92390bac resourceVersion: "49864" uid: 4abbe73c-4c39-4e70-9222-44a00bdb8af9 spec: sourcePod: network-check-source-989f8b8dc-d4gvq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T12:52:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.787µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:16:40Z" - latency: 1.680803ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:16:40Z" - latency: 901.679µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:15:40Z" - latency: 2.095342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:15:40Z" - latency: 789.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:14:40Z" - latency: 2.254504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:14:40Z" - latency: 850.482µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:13:40Z" - latency: 2.08377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:13:40Z" - latency: 1.076344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T13:12:40Z" - latency: 1.814313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T13:12:40Z" kind: List metadata: resourceVersion: ""