apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "60732" uid: a8837f72-c2b0-4ff1-8bd3-3921f0f6cfcc spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-29T23:21:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.485146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 1.422715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 1.127507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 1.044499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:39:30Z" - latency: 1.340802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:38:30Z" - latency: 1.026058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:37:30Z" - latency: 1.587633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:36:30Z" - latency: 1.843054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:35:30Z" - latency: 1.013216ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:34:30Z" - latency: 1.198028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:33:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "62454" uid: f3469267-7e12-4ea9-9dfe-91c5ab8f6f2e spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T23:20:30Z" message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.185403ms message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:44:30Z" - latency: 6.213236ms message: 'load-balancer-api-external: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:44:30Z" - latency: 16.637585ms message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:43:30Z" - latency: 7.86354ms message: 'load-balancer-api-external: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:43:30Z" - latency: 19.321289ms message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 7.631516ms message: 'load-balancer-api-external: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:42:30Z" - latency: 19.722904ms message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 11.880791ms message: 'load-balancer-api-external: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:41:30Z" - latency: 18.303535ms message: 'load-balancer-api-external: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 7.545499ms message: 'load-balancer-api-external: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:40:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "62455" uid: 76e7a5fd-bbb1-4dc2-955b-276bf5ffeeea spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T23:20:30Z" message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.87994ms message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:44:30Z" - latency: 6.157336ms message: 'load-balancer-api-internal: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:44:30Z" - latency: 16.806691ms message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:43:30Z" - latency: 7.793767ms message: 'load-balancer-api-internal: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:43:30Z" - latency: 19.348493ms message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 7.56754ms message: 'load-balancer-api-internal: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:42:30Z" - latency: 16.994595ms message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 11.815673ms message: 'load-balancer-api-internal: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:41:30Z" - latency: 24.589378ms message: 'load-balancer-api-internal: tcp connection to a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 7.478063ms message: 'load-balancer-api-internal: resolved host name a5ae41ff5c01a4f96a569f1e149193ef-bbb98fbe728a5c83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T23:40:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-133-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "60731" uid: 4037c9d0-df2e-4298-8427-16abe00d7235 spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-29T23:21:30Z" message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.568892ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 2.967209ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 2.711007ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 2.35944ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:39:30Z" - latency: 1.938061ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:38:30Z" - latency: 2.409653ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:37:30Z" - latency: 2.562757ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:36:30Z" - latency: 2.625969ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:35:30Z" - latency: 2.150865ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:34:30Z" - latency: 2.618427ms message: 'network-check-target-ip-10-0-133-100: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:33:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-138-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "60763" uid: 1bdae16f-841b-4c7f-a28a-fab9746d06a5 spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-29T23:21:32Z" message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.759103ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:32Z" - latency: 1.011321ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:32Z" - latency: 2.201419ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:32Z" - latency: 961.725µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:39:32Z" - latency: 2.03978ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:38:32Z" - latency: 1.029329ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:37:32Z" - latency: 1.987111ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:36:32Z" - latency: 2.460148ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:35:32Z" - latency: 2.487986ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:34:32Z" - latency: 1.818157ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:33:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-141-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "60730" uid: 901f2c73-afba-407f-b31e-6dfb6202c402 spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-29T23:21:30Z" message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.374742ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 1.039266ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 1.009707ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 1.015216ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:39:30Z" - latency: 848.615µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:38:30Z" - latency: 865.152µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:37:30Z" - latency: 1.243996ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:36:30Z" - latency: 941.275µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:35:30Z" - latency: 833.055µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:34:30Z" - latency: 1.046075ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:33:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T23:14:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: d8ee5227-bbf6-4497-a1cb-de2d015000fe resourceVersion: "62453" uid: c226f5b9-ee92-48c5-8bb8-0f2367b62583 spec: sourcePod: network-check-source-6f78d59f99-6djdh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-29T23:20:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14953ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:44:30Z" - latency: 1.634872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:44:30Z" - latency: 1.239961ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:43:30Z" - latency: 2.414693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:43:30Z" - latency: 971.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:42:30Z" - latency: 2.298338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:42:30Z" - latency: 2.24922ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:41:30Z" - latency: 1.949223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:41:30Z" - latency: 1.204904ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T23:40:30Z" - latency: 1.967654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T23:40:30Z" kind: List metadata: resourceVersion: ""