apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "54041" uid: 96eb9e1b-516e-4641-81e2-5bcc8404a319 spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:52:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 886.018µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 1.070543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 1.071816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 899.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:25Z" - latency: 1.104517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:25Z" - latency: 864.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:25Z" - latency: 848.261µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:25Z" - latency: 853.231µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:25Z" - latency: 1.074301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "55095" uid: 6219a9fc-bfac-4518-853f-018985f1b51f spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:51:25Z" message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.674265ms message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:21:25Z" - latency: 11.42685ms message: 'load-balancer-api-external: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:25Z" - latency: 3.731541ms message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 8.014832ms message: 'load-balancer-api-external: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:25Z" - latency: 3.692788ms message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 8.938788ms message: 'load-balancer-api-external: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:25Z" - latency: 4.091355ms message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 7.744989ms message: 'load-balancer-api-external: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:25Z" - latency: 5.22451ms message: 'load-balancer-api-external: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 8.349747ms message: 'load-balancer-api-external: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "55094" uid: 807af5d3-9609-42c7-a2db-c870016f098c spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:51:25Z" message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.641178ms message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:21:25Z" - latency: 11.4854ms message: 'load-balancer-api-internal: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:25Z" - latency: 4.113496ms message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 8.128886ms message: 'load-balancer-api-internal: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:25Z" - latency: 3.733211ms message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 8.895643ms message: 'load-balancer-api-internal: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:25Z" - latency: 4.029566ms message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 7.794093ms message: 'load-balancer-api-internal: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:25Z" - latency: 5.431423ms message: 'load-balancer-api-internal: tcp connection to ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 8.410835ms message: 'load-balancer-api-internal: resolved host name ac687a289c09c473ebd6c39f38fec2ef-bd6d341749092aa8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-128-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "54040" uid: d4b94adb-93ec-4ddd-b803-b434bf9aa103 spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:25Z" message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.543753ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 1.922856ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 2.335561ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 1.928025ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 2.274109ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:25Z" - latency: 2.41231ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:25Z" - latency: 2.361158ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:25Z" - latency: 2.390231ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:25Z" - latency: 2.328683ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:25Z" - latency: 2.511404ms message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-132-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "54039" uid: 14ca8693-317d-41aa-af6c-e3e73687c069 spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:25Z" message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.587966ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 2.082189ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 2.383652ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 2.48195ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 2.184869ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:25Z" - latency: 2.134659ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:25Z" - latency: 2.072579ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:25Z" - latency: 2.339167ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:25Z" - latency: 2.338577ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:25Z" - latency: 2.281809ms message: 'network-check-target-ip-10-0-132-65: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-141-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "54038" uid: 1361df06-63a7-4ef1-b9aa-90e5a3d293da spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:52:25Z" message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.912µs message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 789.517µs message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 1.33079ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 1.005422ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 1.020452ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:25Z" - latency: 1.552315ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:25Z" - latency: 1.377882ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:25Z" - latency: 1.042065ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:25Z" - latency: 974.525µs message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:25Z" - latency: 1.162341ms message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:45:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-63.ec2.internal uid: fa0d65c3-e174-4156-b3dd-cdb7b52d726e resourceVersion: "55093" uid: 2a4372da-cdfb-4ee5-b827-2aad684a7da0 spec: sourcePod: network-check-source-989f8b8dc-fzwmm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:51:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - 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-07T16:21:25Z" - latency: 1.617485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:21:25Z" - latency: 997.501µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:20:25Z" - latency: 1.689004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:20:25Z" - latency: 929.525µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:25Z" - latency: 1.711533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:25Z" - latency: 1.283151ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:25Z" - latency: 1.633746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:25Z" - latency: 984.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:25Z" - latency: 1.773504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:25Z" kind: List metadata: resourceVersion: ""