apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63996" uid: 9843f0b3-5f03-4c91-9d1c-d6ab5bb0c233 spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T18:56:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.735289ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 1.192134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 1.658857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 1.475545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 1.216787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 1.172324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:09Z" - latency: 960.206µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:09Z" - latency: 1.449408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:09Z" - latency: 1.201726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:09Z" - latency: 979.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63997" uid: 7ef292cc-fa82-4d55-bd65-403828d9d608 spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:55:09Z" message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.190736ms message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 11.492275ms message: 'load-balancer-api-external: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:31:09Z" - latency: 4.764273ms message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 7.518653ms message: 'load-balancer-api-external: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:30:09Z" - latency: 4.635497ms message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 8.007966ms message: 'load-balancer-api-external: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:29:09Z" - latency: 3.472275ms message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 7.031983ms message: 'load-balancer-api-external: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:09Z" - latency: 5.750368ms message: 'load-balancer-api-external: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 7.344984ms message: 'load-balancer-api-external: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63998" uid: 1cee244c-e64b-41e6-9fcc-64bdd0b15c37 spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:55:09Z" message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.182828ms message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 11.706989ms message: 'load-balancer-api-internal: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:31:09Z" - latency: 5.298587ms message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 7.569386ms message: 'load-balancer-api-internal: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:30:09Z" - latency: 4.311672ms message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 7.975643ms message: 'load-balancer-api-internal: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:29:09Z" - latency: 5.047572ms message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 7.016517ms message: 'load-balancer-api-internal: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:09Z" - latency: 5.7864ms message: 'load-balancer-api-internal: tcp connection to a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 7.514243ms message: 'load-balancer-api-internal: resolved host name a76e3e23bb2e746818bb1d1f51955f42-fc62357410cd0f15.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-network-check-target-ip-10-0-131-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63995" uid: e3df8e35-ba97-41d9-8913-5e3e488a3faf spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:56:09Z" message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.746765ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 2.366088ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 2.822757ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 1.913722ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 3.009706ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 2.129297ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:09Z" - latency: 2.329621ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:09Z" - latency: 3.015599ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:09Z" - latency: 2.311425ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:09Z" - latency: 2.67035ms message: 'network-check-target-ip-10-0-131-36: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-network-check-target-ip-10-0-137-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63993" uid: 8307aa69-610f-45ed-aec2-151f11cb37b9 spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:56:09Z" message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.327809ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 2.571179ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 2.689936ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 2.366055ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 2.72318ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 2.701719ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:09Z" - latency: 2.173646ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:09Z" - latency: 2.530875ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:09Z" - latency: 1.9212ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:09Z" - latency: 2.333507ms message: 'network-check-target-ip-10-0-137-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-network-check-target-ip-10-0-138-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63992" uid: b8789775-28b3-483d-babe-18dd4f0c1f19 spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:56:09Z" message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.124208ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 1.394259ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 1.191535ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 1.078869ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 1.660015ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 1.790858ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:26:09Z" - latency: 1.116897ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:25:09Z" - latency: 1.507361ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:24:09Z" - latency: 1.004177ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:23:09Z" - latency: 986.961µs message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:22:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:49:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-140-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-140.ec2.internal uid: dfb2ce5b-9c3e-4596-a569-76785d3562ac resourceVersion: "63994" uid: 58200d89-285c-44cf-acf9-14a4ad0f587d spec: sourcePod: network-check-source-7bc5b6bf85-7n7z5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T18:55:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.145374ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:31:09Z" - latency: 2.757911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:31:09Z" - latency: 1.150577ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:30:09Z" - latency: 2.013119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:30:09Z" - latency: 999.554µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:29:09Z" - latency: 2.466707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:29:09Z" - latency: 1.137455ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:28:09Z" - latency: 2.302097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:28:09Z" - latency: 1.348669ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T19:27:09Z" - latency: 2.34819ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T19:27:09Z" kind: List metadata: resourceVersion: ""