apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "68150" uid: da68fea6-c0d3-44a2-aec7-848d940b41e1 spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T09:29:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:13Z" - latency: 1.681907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:13Z" - latency: 1.238938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:09:13Z" - latency: 1.013722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:08:13Z" - latency: 1.210292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:07:13Z" - latency: 959.598µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:06:13Z" - latency: 849.966µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:05:13Z" - latency: 876.146µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:04:13Z" - latency: 1.023272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:03:13Z" - latency: 947.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:02:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "73934" uid: 5d455411-9ebe-4cfa-9860-3eee304a358d spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T09:28:13Z" message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.329353ms message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:13Z" - latency: 6.339076ms message: 'load-balancer-api-external: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:13Z" - latency: 4.171127ms message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:13Z" - latency: 6.362635ms message: 'load-balancer-api-external: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:13Z" - latency: 4.404339ms message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:13Z" - latency: 6.529292ms message: 'load-balancer-api-external: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:13Z" - latency: 6.094691ms message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:13Z" - latency: 6.431919ms message: 'load-balancer-api-external: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:13:13Z" - latency: 6.435178ms message: 'load-balancer-api-external: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:13Z" - latency: 6.771633ms message: 'load-balancer-api-external: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:12:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "73933" uid: 3854abf9-90f1-4e07-a669-fba1666dbb0e spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T09:28:13Z" message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.356194ms message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:13Z" - latency: 6.271073ms message: 'load-balancer-api-internal: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:13Z" - latency: 5.149621ms message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:13Z" - latency: 6.423262ms message: 'load-balancer-api-internal: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:13Z" - latency: 4.289046ms message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:13Z" - latency: 6.552078ms message: 'load-balancer-api-internal: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:13Z" - latency: 6.069184ms message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:13Z" - latency: 6.465071ms message: 'load-balancer-api-internal: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:13:13Z" - latency: 5.414056ms message: 'load-balancer-api-internal: tcp connection to aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:13Z" - latency: 6.719324ms message: 'load-balancer-api-internal: resolved host name aa942d10396c64faba8e5a6704bb6634-b80e851cd7498e5c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T10:12:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-network-check-target-ip-10-0-131-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "68148" uid: d182eab6-05a7-4d77-b387-34fbc9bd3def spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:29:13Z" message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.278376ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:13Z" - latency: 2.469215ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:13Z" - latency: 2.264314ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:09:13Z" - latency: 2.195182ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:08:13Z" - latency: 2.452938ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:07:13Z" - latency: 2.295808ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:06:13Z" - latency: 2.544785ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:05:13Z" - latency: 2.163079ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:04:13Z" - latency: 2.258669ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:03:13Z" - latency: 2.579548ms message: 'network-check-target-ip-10-0-131-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:02:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-network-check-target-ip-10-0-138-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "68147" uid: 88dadce0-fe90-49dd-9e16-7a81880b9e42 spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:29:13Z" message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.031322ms message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:13Z" - latency: 1.506601ms message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:13Z" - latency: 908.751µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:09:13Z" - latency: 861.948µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:08:13Z" - latency: 1.213896ms message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:07:13Z" - latency: 906.703µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:06:13Z" - latency: 980.475µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:05:13Z" - latency: 842.496µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:04:13Z" - latency: 875.149µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:03:13Z" - latency: 940.196µs message: 'network-check-target-ip-10-0-138-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:02:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-network-check-target-ip-10-0-139-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "68149" uid: 6e8be8d4-4f41-4850-945d-601d5ad58524 spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T09:29:13Z" message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381959ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:11:13Z" - latency: 2.584241ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:10:13Z" - latency: 1.857668ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:09:13Z" - latency: 2.389025ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:08:13Z" - latency: 2.375736ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:07:13Z" - latency: 2.387717ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:06:13Z" - latency: 2.180633ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:05:13Z" - latency: 1.8486ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:04:13Z" - latency: 2.370588ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:03:13Z" - latency: 2.535634ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:02:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T09:22:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-208-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-208.ec2.internal uid: 099c73e6-cac3-4ebb-959b-8117de49b8e0 resourceVersion: "73932" uid: c9859266-e7c4-4381-a303-5ccbdee3f87d spec: sourcePod: network-check-source-7bc5b6bf85-kssqm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T09:28:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.066672ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:16:13Z" - latency: 2.146246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:16:13Z" - latency: 988.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:15:13Z" - latency: 1.515995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:15:13Z" - latency: 1.13754ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:14:13Z" - latency: 1.976212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:14:13Z" - latency: 1.414868ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:13:13Z" - latency: 1.597079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:13:13Z" - latency: 989.114µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T10:12:13Z" - latency: 1.732361ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T10:12:13Z" kind: List metadata: resourceVersion: ""