apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "25978" uid: b86e7954-447c-4e59-a8b2-5e4cf645f9e1 spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:19:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.679212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 1.276964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 989.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 1.32766ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:43Z" - latency: 1.101822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:43Z" - latency: 970.151µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:43Z" - latency: 1.136245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:43Z" - latency: 1.201808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:43Z" - latency: 1.06259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:43Z" - latency: 1.05026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "26941" uid: 09224386-6fdf-4917-9d19-da04b29620e9 spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:18:43Z" message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.379645ms message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:43Z" - latency: 8.060442ms message: 'load-balancer-api-external: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:43Z" - latency: 4.804569ms message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:43Z" - latency: 9.290521ms message: 'load-balancer-api-external: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:43Z" - latency: 5.271335ms message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 7.832744ms message: 'load-balancer-api-external: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:43Z" - latency: 5.18988ms message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 8.707733ms message: 'load-balancer-api-external: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:43Z" - latency: 5.760679ms message: 'load-balancer-api-external: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 9.719825ms message: 'load-balancer-api-external: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "26940" uid: cb58b9d7-da05-41f6-8670-46c87387302b spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:18:43Z" message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.438964ms message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:43Z" - latency: 8.08242ms message: 'load-balancer-api-internal: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:43Z" - latency: 4.9879ms message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:43Z" - latency: 9.206749ms message: 'load-balancer-api-internal: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:43Z" - latency: 5.718806ms message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 7.887568ms message: 'load-balancer-api-internal: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:43Z" - latency: 5.223099ms message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 8.630257ms message: 'load-balancer-api-internal: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:43Z" - latency: 5.882238ms message: 'load-balancer-api-internal: tcp connection to a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 9.655309ms message: 'load-balancer-api-internal: resolved host name a2753a32049e545c5a5041cda90026cf-2daf0f7828d6dd6e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-128-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "25977" uid: dfe2aa7e-66af-424e-ac21-9a8d19e37510 spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:19:43Z" message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.487788ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 2.660423ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 2.334459ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 2.224503ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:43Z" - latency: 2.297669ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:43Z" - latency: 2.321146ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:43Z" - latency: 2.256362ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:43Z" - latency: 2.110727ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:43Z" - latency: 2.227279ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:43Z" - latency: 2.451656ms message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-138-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "25975" uid: 59b061ef-a7db-403b-a552-139b696da661 spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:19:43Z" message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 773.742µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 873.246µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 876.646µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 1.480652ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:43Z" - latency: 923.532µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:43Z" - latency: 962.963µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:43Z" - latency: 982.96µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:43Z" - latency: 938.272µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:43Z" - latency: 1.167559ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:43Z" - latency: 825.345µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-139-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "25976" uid: 0943e278-4142-45a7-9602-3cfa809d7b5f spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:19:43Z" message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.340147ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 2.391802ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 2.260499ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 2.2249ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:37:43Z" - latency: 2.201353ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:36:43Z" - latency: 2.331586ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:35:43Z" - latency: 2.283686ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:34:43Z" - latency: 2.133901ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:33:43Z" - latency: 2.151678ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:32:43Z" - latency: 2.272593ms message: 'network-check-target-ip-10-0-139-137: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:31:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:12:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: fcd33ec3-4241-4b13-9a3e-b59345a5d12a resourceVersion: "26939" uid: aea55026-637a-431b-bfe2-460d466d98e7 spec: sourcePod: network-check-source-7d88cb55d8-q5m5c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:18:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002206ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:42:43Z" - latency: 1.753669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:42:43Z" - latency: 1.452067ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:41:43Z" - latency: 1.782345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:41:43Z" - latency: 881.147µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:40:43Z" - latency: 2.241755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:40:43Z" - latency: 979.255µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:39:43Z" - latency: 2.146072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:39:43Z" - latency: 1.08237ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:38:43Z" - latency: 1.791253ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:38:43Z" kind: List metadata: resourceVersion: ""