apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "61130" uid: 52d440b8-b266-46e0-b681-b52029ef34a4 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T19:01:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 1.310879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 1.084408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 1.061696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:19:55Z" - latency: 1.63116ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:18:55Z" - latency: 933.673µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:17:55Z" - latency: 1.096317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:16:55Z" - latency: 1.074336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:15:55Z" - latency: 1.059842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:14:55Z" - latency: 1.112371ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:13:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "62677" uid: a0266146-1797-450f-84cd-729a991434a6 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T19:00:55Z" message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.462937ms message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:24:55Z" - latency: 10.825914ms message: 'load-balancer-api-external: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:24:55Z" - latency: 4.874797ms message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:23:55Z" - latency: 12.076563ms message: 'load-balancer-api-external: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:23:55Z" - latency: 4.683594ms message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 9.592232ms message: 'load-balancer-api-external: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:22:55Z" - latency: 5.779316ms message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 8.454677ms message: 'load-balancer-api-external: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:21:55Z" - latency: 4.480703ms message: 'load-balancer-api-external: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 7.277998ms message: 'load-balancer-api-external: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:20:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "62679" uid: 761750b1-3c87-4d20-b050-5313eb9c57d0 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T19:00:55Z" message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.987457ms message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:24:55Z" - latency: 10.834718ms message: 'load-balancer-api-internal: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:24:55Z" - latency: 4.468952ms message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:23:55Z" - latency: 11.997733ms message: 'load-balancer-api-internal: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:23:55Z" - latency: 4.736173ms message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 9.522279ms message: 'load-balancer-api-internal: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:22:55Z" - latency: 5.80848ms message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 8.375354ms message: 'load-balancer-api-internal: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:21:55Z" - latency: 4.472863ms message: 'load-balancer-api-internal: tcp connection to ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 7.322025ms message: 'load-balancer-api-internal: resolved host name ad0d44ca70c944b9b83ec20fee457d1c-bce910999d0a0577.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T19:20:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-129-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "61128" uid: 36ad88f8-38db-4099-9fc9-11b060215e14 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T19:01:55Z" message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.426335ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 2.284563ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 2.247493ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 1.95248ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:19:55Z" - latency: 2.667004ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:18:55Z" - latency: 2.853459ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:17:55Z" - latency: 2.526781ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:16:55Z" - latency: 3.235958ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:15:55Z" - latency: 2.211275ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:14:55Z" - latency: 2.089149ms message: 'network-check-target-ip-10-0-129-227: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:13:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-129-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "61127" uid: 4c31d5b1-44b0-42ec-b1ff-6236cf995ab6 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T19:01:55Z" message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16946ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 1.557416ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 1.033629ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 896.143µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:19:55Z" - latency: 1.178136ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:18:55Z" - latency: 1.093882ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:17:55Z" - latency: 1.297002ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:16:55Z" - latency: 1.843699ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:15:55Z" - latency: 877.984µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:14:55Z" - latency: 1.026393ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:13:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-132-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "61129" uid: b607af33-fe92-4833-9680-50101757f94c spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T19:01:55Z" message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.435251ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 2.750692ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 2.253931ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 2.6296ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:19:55Z" - latency: 3.097962ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:18:55Z" - latency: 2.705557ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:17:55Z" - latency: 2.441605ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:16:55Z" - latency: 2.594639ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:15:55Z" - latency: 2.738131ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:14:55Z" - latency: 2.715001ms message: 'network-check-target-ip-10-0-132-28: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:13:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T18:54:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.ec2.internal uid: 34ed9377-f5d0-45d7-9a5b-77f42a2bbb62 resourceVersion: "62676" uid: a7971c4c-7b0b-4437-a6be-96d59c8b26b6 spec: sourcePod: network-check-source-6f8b768455-dcfqp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T19:00:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090418ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:24:55Z" - latency: 1.93403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T19:24:55Z" - latency: 1.814286ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:23:55Z" - latency: 1.926374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T19:23:55Z" - latency: 1.171779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:22:55Z" - latency: 2.175915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T19:22:55Z" - latency: 1.074267ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:21:55Z" - latency: 2.245772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T19:21:55Z" - latency: 1.052264ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T19:20:55Z" - latency: 1.869696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T19:20:55Z" kind: List metadata: resourceVersion: ""