apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "54344" uid: a9e5c5be-f696-428b-94ad-d362b6fbdf15 spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T04:52:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.155217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 1.079435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 866.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 982.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:10:21Z" - latency: 1.326233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:09:21Z" - latency: 1.125817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:08:21Z" - latency: 1.088265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:07:21Z" - latency: 1.10087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:06:21Z" - latency: 1.503094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:05:21Z" - latency: 1.22347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:04:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "55966" uid: 9d36d19b-13d5-4f8b-947e-3cd93a2c6753 spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T04:51:21Z" message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.881045ms message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:15:21Z" - latency: 8.42095ms message: 'load-balancer-api-external: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:15:21Z" - latency: 3.966386ms message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:14:21Z" - latency: 8.408337ms message: 'load-balancer-api-external: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:14:21Z" - latency: 4.940039ms message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 8.810399ms message: 'load-balancer-api-external: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:13:21Z" - latency: 5.150824ms message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 9.276957ms message: 'load-balancer-api-external: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:12:21Z" - latency: 4.935821ms message: 'load-balancer-api-external: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 8.370703ms message: 'load-balancer-api-external: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "55965" uid: d376c666-cd54-45b4-984f-8d3d0f55b0bc spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T04:51:21Z" message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.821943ms message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:15:21Z" - latency: 8.340335ms message: 'load-balancer-api-internal: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:15:21Z" - latency: 3.876119ms message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:14:21Z" - latency: 8.479047ms message: 'load-balancer-api-internal: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:14:21Z" - latency: 5.555926ms message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 8.858659ms message: 'load-balancer-api-internal: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:13:21Z" - latency: 3.973814ms message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 9.303469ms message: 'load-balancer-api-internal: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:12:21Z" - latency: 4.951471ms message: 'load-balancer-api-internal: tcp connection to ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 8.323266ms message: 'load-balancer-api-internal: resolved host name ac3232b46adf640648a846480a2e3a71-5c66a6bdc2c3d8a2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T05:11:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-network-check-target-ip-10-0-132-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "54342" uid: bb9afeec-ea4c-409d-9c7a-770a9562789c spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T04:52:21Z" message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.086464ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 2.486526ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 2.412399ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 2.297719ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:10:21Z" - latency: 2.313255ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:09:21Z" - latency: 2.46796ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:08:21Z" - latency: 2.386184ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:07:21Z" - latency: 2.238207ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:06:21Z" - latency: 2.841872ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:05:21Z" - latency: 2.14592ms message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:04:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-network-check-target-ip-10-0-136-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "54343" uid: b26e7dec-a1e7-4960-96dd-6caca358f67f spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T04:52:21Z" message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.371648ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 2.500447ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 2.544962ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 2.555053ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:10:21Z" - latency: 2.330082ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:09:21Z" - latency: 2.50259ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:08:21Z" - latency: 2.490082ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:07:21Z" - latency: 2.525021ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:06:21Z" - latency: 2.651121ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:05:21Z" - latency: 2.108377ms message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:04:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-network-check-target-ip-10-0-138-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "54341" uid: 4f0faf28-4c46-4004-9d01-589b037f770a spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T04:52:21Z" message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186376ms message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 945.717µs message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 906.843µs message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 932.014µs message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:10:21Z" - latency: 889.63µs message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:09:21Z" - latency: 1.045172ms message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:08:21Z" - latency: 926.678µs message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:07:21Z" - latency: 1.289467ms message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:06:21Z" - latency: 1.033561ms message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:05:21Z" - latency: 1.339595ms message: 'network-check-target-ip-10-0-138-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:04:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T04:45:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-27.ec2.internal uid: 9bb9e91a-c395-4e62-9381-e50f7db06453 resourceVersion: "55964" uid: 12a2965e-6019-45c9-a950-690805aa0f19 spec: sourcePod: network-check-source-685456655f-hnd48 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T04:51:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.045242ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:15:21Z" - latency: 1.767523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T05:15:21Z" - latency: 771.422µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:14:21Z" - latency: 1.948253ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T05:14:21Z" - latency: 1.042201ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:13:21Z" - latency: 2.150024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T05:13:21Z" - latency: 785.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:12:21Z" - latency: 2.03378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T05:12:21Z" - latency: 1.285752ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T05:11:21Z" - latency: 1.701852ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T05:11:21Z" kind: List metadata: resourceVersion: ""