apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62799" uid: 299b75d0-e795-4855-85f6-e465c492b9c2 spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T16:40:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 944.87µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 899.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 1.107673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 891.733µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 940.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:10:52Z" - latency: 925.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:09:52Z" - latency: 981.898µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:08:52Z" - latency: 1.395727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:07:52Z" - latency: 951.394µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62801" uid: 614e1481-e533-4e66-a616-4fc46a6aaad6 spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:39:52Z" message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.338413ms message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 12.537165ms message: 'load-balancer-api-external: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:15:52Z" - latency: 3.626833ms message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 12.808755ms message: 'load-balancer-api-external: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:14:52Z" - latency: 4.921761ms message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 12.205796ms message: 'load-balancer-api-external: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:13:52Z" - latency: 4.22316ms message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 7.153628ms message: 'load-balancer-api-external: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:12:52Z" - latency: 3.805453ms message: 'load-balancer-api-external: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 7.167035ms message: 'load-balancer-api-external: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:11:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62802" uid: 7e736c69-ad16-4926-807c-d162ca0b033c spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:39:52Z" message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.722734ms message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 12.661709ms message: 'load-balancer-api-internal: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:15:52Z" - latency: 5.36668ms message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 12.843708ms message: 'load-balancer-api-internal: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:14:52Z" - latency: 4.882203ms message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 12.16968ms message: 'load-balancer-api-internal: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:13:52Z" - latency: 4.232312ms message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 7.112312ms message: 'load-balancer-api-internal: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:12:52Z" - latency: 4.924591ms message: 'load-balancer-api-internal: tcp connection to ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 7.19622ms message: 'load-balancer-api-internal: resolved host name ada5004ebd6c9416caf2872c8b9819cf-84733d88c07e0238.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:11:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-network-check-target-ip-10-0-130-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62795" uid: 9130cd1a-03a1-4208-bf39-e10cdd53dc96 spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:40:52Z" message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.791555ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 2.342866ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 2.296458ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 2.319486ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 2.221658ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 2.50658ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:10:52Z" - latency: 2.329921ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:09:52Z" - latency: 2.372296ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:08:52Z" - latency: 2.472167ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:07:52Z" - latency: 2.118713ms message: 'network-check-target-ip-10-0-130-209: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-network-check-target-ip-10-0-130-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62796" uid: ffde7d86-d382-4054-8bda-01d204c7190b spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:40:52Z" message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.77125ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 1.946214ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 1.713766ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 1.997711ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 1.724464ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 1.887217ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:10:52Z" - latency: 1.698644ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:09:52Z" - latency: 1.732795ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:08:52Z" - latency: 1.859991ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:07:52Z" - latency: 1.862461ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-network-check-target-ip-10-0-133-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62797" uid: e86f41e3-32c6-4183-af29-05dcff43d2d5 spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:40:52Z" message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.598µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 1.085315ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 993.599µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 869.821µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 917.646µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 913.247µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:10:52Z" - latency: 1.250115ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:09:52Z" - latency: 1.404183ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:08:52Z" - latency: 1.381052ms message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:07:52Z" - latency: 897.37µs message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:06:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:33:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-157-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-157.ec2.internal uid: b5afade0-5e3a-4325-84c2-65389f52621d resourceVersion: "62798" uid: 667b2b58-a968-41de-82ab-dbd95544fbe9 spec: sourcePod: network-check-source-7bc5b6bf85-w24p9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T16:39:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 933.139µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:15:52Z" - latency: 1.786184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:15:52Z" - latency: 1.073536ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:14:52Z" - latency: 1.816996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:14:52Z" - latency: 735.41µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:13:52Z" - latency: 1.908463ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:13:52Z" - latency: 1.04085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:12:52Z" - latency: 2.165124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:12:52Z" - latency: 1.039942ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:11:52Z" - latency: 1.889534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:11:52Z" kind: List metadata: resourceVersion: ""