apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "76672" uid: 8fd5a001-aac1-430c-817a-da2a508cd830 spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-26T15:48:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 790.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:30:01Z" - latency: 926.588µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 1.228516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 892.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 1.145061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 1.210275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 908.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:24:01Z" - latency: 1.107426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:23:01Z" - latency: 1.263793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:22:01Z" - latency: 979.479µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:21:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "74754" uid: 890db6c1-60b4-4ae6-803e-6c6133a8b90f spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T15:47:01Z" message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.134944ms message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 6.504192ms message: 'load-balancer-api-external: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:29:01Z" - latency: 5.187462ms message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 6.933523ms message: 'load-balancer-api-external: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:28:01Z" - latency: 4.448572ms message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 7.777235ms message: 'load-balancer-api-external: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:27:01Z" - latency: 5.479478ms message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 6.970148ms message: 'load-balancer-api-external: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:26:01Z" - latency: 3.555066ms message: 'load-balancer-api-external: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 7.178899ms message: 'load-balancer-api-external: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:25:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "74753" uid: 2afe4228-0e67-41a7-93ea-8ebd2990470d spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T15:47:01Z" message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.123722ms message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 6.529956ms message: 'load-balancer-api-internal: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:29:01Z" - latency: 5.125533ms message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 6.991296ms message: 'load-balancer-api-internal: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:28:01Z" - latency: 4.881264ms message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 7.748717ms message: 'load-balancer-api-internal: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:27:01Z" - latency: 5.817475ms message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 6.923953ms message: 'load-balancer-api-internal: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:26:01Z" - latency: 3.540368ms message: 'load-balancer-api-internal: tcp connection to abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 7.125079ms message: 'load-balancer-api-internal: resolved host name abd87a377598947e7b6338c663179148-dcbf00ea249e73bb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T16:25:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-network-check-target-ip-10-0-132-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "76671" uid: f59972e0-4303-4413-935e-bbb72ad3a3b0 spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T15:48:01Z" message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381125ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:30:01Z" - latency: 2.049128ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 2.092889ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 1.858383ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 2.363242ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 2.058881ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 2.429821ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:24:01Z" - latency: 2.245191ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:23:01Z" - latency: 2.393243ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:22:01Z" - latency: 2.494802ms message: 'network-check-target-ip-10-0-132-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:21:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-network-check-target-ip-10-0-138-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "76670" uid: 03bd0d36-d257-401b-802b-c459119348a2 spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T15:48:01Z" message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.498723ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:30:01Z" - latency: 2.236451ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 2.348631ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 2.430481ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 2.057731ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 2.332131ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 2.341728ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:24:01Z" - latency: 2.375191ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:23:01Z" - latency: 2.435052ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:22:01Z" - latency: 2.396339ms message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:21:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-network-check-target-ip-10-0-138-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "76669" uid: e08a23e3-191c-46e2-8f81-5cccf7e6f064 spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-26T15:48:01Z" message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.864µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:30:01Z" - latency: 980.426µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 1.177972ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 1.477289ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 965.761µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 875.491µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 953.318µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:24:01Z" - latency: 972.204µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:23:01Z" - latency: 1.767392ms message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:22:01Z" - latency: 934.454µs message: 'network-check-target-ip-10-0-138-163: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:21:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T15:41:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-163-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-163.ec2.internal uid: feff1e21-0c38-49fc-b7a7-50a409099112 resourceVersion: "74751" uid: d798f596-3b2d-4dc6-b0f5-0717901128f5 spec: sourcePod: network-check-source-7d88cb55d8-5zpk2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-26T15:47:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.667µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:29:01Z" - latency: 2.127975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:29:01Z" - latency: 1.005044ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:28:01Z" - latency: 1.940501ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:28:01Z" - latency: 1.632649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:27:01Z" - latency: 1.773342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:27:01Z" - latency: 926.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:26:01Z" - latency: 2.100401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:26:01Z" - latency: 992.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T16:25:01Z" - latency: 1.784394ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T16:25:01Z" kind: List metadata: resourceVersion: ""