apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32501" uid: 759f0709-4125-49ac-93aa-1cc1a3951107 spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:46:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.304387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 1.342739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 1.138313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 1.514475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 1.043193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 1.333874ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:18Z" - latency: 1.07498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:18Z" - latency: 1.002598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:18Z" - latency: 1.179318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:18Z" - latency: 1.310097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32503" uid: d411c049-6817-4204-b64a-97cf52b9f45c spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:45:18Z" message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.445687ms message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 7.921805ms message: 'load-balancer-api-external: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:18Z" - latency: 5.558677ms message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 7.002673ms message: 'load-balancer-api-external: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:18Z" - latency: 5.79642ms message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 7.244236ms message: 'load-balancer-api-external: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:18Z" - latency: 3.77209ms message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 6.261266ms message: 'load-balancer-api-external: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:18Z" - latency: 5.591548ms message: 'load-balancer-api-external: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 8.285775ms message: 'load-balancer-api-external: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32504" uid: f236a3e4-e2ca-4634-9ac8-1950f8a81acb spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:45:18Z" message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.399856ms message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 7.955232ms message: 'load-balancer-api-internal: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:18Z" - latency: 5.584356ms message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 6.966948ms message: 'load-balancer-api-internal: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:18Z" - latency: 5.80865ms message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 7.298389ms message: 'load-balancer-api-internal: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:18Z" - latency: 5.239121ms message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 6.357225ms message: 'load-balancer-api-internal: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:18Z" - latency: 5.598032ms message: 'load-balancer-api-internal: tcp connection to abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 8.223496ms message: 'load-balancer-api-internal: resolved host name abc999b0188364e81bcb1cd69ff81a38-8bd8a038327f47f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-network-check-target-ip-10-0-135-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32497" uid: 1185ffd0-750f-40b4-817c-9b41951d005e spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:18Z" message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.116µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 949.172µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 1.080106ms message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 804.772µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 987.319µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 916.845µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:18Z" - latency: 1.156265ms message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:18Z" - latency: 1.359563ms message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:18Z" - latency: 933.266µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:18Z" - latency: 998.425µs message: 'network-check-target-ip-10-0-135-249: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-network-check-target-ip-10-0-139-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32499" uid: 56fe008b-f1cd-4c5b-8823-1702f2613f5b spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:18Z" message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.520125ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 2.46124ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 2.243395ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 2.243506ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 1.904524ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 2.24424ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:18Z" - latency: 2.297475ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:18Z" - latency: 2.337028ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:18Z" - latency: 2.245886ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:18Z" - latency: 2.465662ms message: 'network-check-target-ip-10-0-139-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-network-check-target-ip-10-0-141-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32498" uid: 58f093dc-db5f-4506-a3c4-8d39a0943fd6 spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:18Z" message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.145659ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 2.154043ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 2.103761ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 2.498056ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 1.97967ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 1.999519ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:18Z" - latency: 1.969234ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:18Z" - latency: 1.787862ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:18Z" - latency: 1.75232ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:18Z" - latency: 2.039171ms message: 'network-check-target-ip-10-0-141-151: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-249.ec2.internal uid: 3032dcef-a2a2-4240-b7c0-17198b9caa2f resourceVersion: "32500" uid: 1a19d37c-3aa1-4267-af0c-63047a6406a2 spec: sourcePod: network-check-source-869dcfcdcd-kc2td targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:45:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.274µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:21:18Z" - latency: 2.008517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:21:18Z" - latency: 975.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:18Z" - latency: 2.01946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:18Z" - latency: 1.28089ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:18Z" - latency: 1.727733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:18Z" - latency: 1.055111ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:18Z" - latency: 1.874254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:18Z" - latency: 960.22µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:18Z" - latency: 2.638142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:18Z" kind: List metadata: resourceVersion: ""