apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "92951" uid: 5edda784-8c47-4f56-9a43-5a5cdd5f4418 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T05:59:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 1.357049ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:29:56Z" - latency: 1.395793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:28:56Z" - latency: 1.16928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:27:56Z" - latency: 1.027161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:26:56Z" - latency: 1.221976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:25:56Z" - latency: 1.097213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:24:56Z" - latency: 1.296101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:23:56Z" - latency: 1.180239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:22:56Z" - latency: 1.184706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "96259" uid: 2c12a748-c18f-4cfd-b1b6-2b3a921d12f0 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T05:58:56Z" message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.867561ms message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:34:56Z" - latency: 7.121316ms message: 'load-balancer-api-external: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:34:56Z" - latency: 3.971938ms message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:33:56Z" - latency: 7.6607ms message: 'load-balancer-api-external: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:33:56Z" - latency: 5.009997ms message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:32:56Z" - latency: 7.183031ms message: 'load-balancer-api-external: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:32:56Z" - latency: 5.020882ms message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:31:56Z" - latency: 12.138094ms message: 'load-balancer-api-external: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:31:56Z" - latency: 3.578419ms message: 'load-balancer-api-external: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 7.393844ms message: 'load-balancer-api-external: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "96260" uid: f219ba77-9e2e-46ec-b89b-f99f78944466 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T05:58:56Z" message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.472039ms message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:34:56Z" - latency: 7.091345ms message: 'load-balancer-api-internal: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:34:56Z" - latency: 7.381934ms message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:33:56Z" - latency: 7.713549ms message: 'load-balancer-api-internal: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:33:56Z" - latency: 4.388632ms message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:32:56Z" - latency: 7.132057ms message: 'load-balancer-api-internal: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:32:56Z" - latency: 5.003211ms message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:31:56Z" - latency: 12.23665ms message: 'load-balancer-api-internal: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:31:56Z" - latency: 4.881415ms message: 'load-balancer-api-internal: tcp connection to a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 7.347553ms message: 'load-balancer-api-internal: resolved host name a15f160cb9fc049e090daca22bfeb390-08bf69e8cbd20e94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T07:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-network-check-target-ip-10-0-128-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "92948" uid: 1bf4a5b0-28d9-47d5-a4bb-b02ee89b72d8 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:59:56Z" message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.155475ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 1.884138ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:29:56Z" - latency: 1.892531ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:28:56Z" - latency: 2.25223ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:27:56Z" - latency: 2.153839ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:26:56Z" - latency: 1.957898ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:25:56Z" - latency: 2.101525ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:24:56Z" - latency: 1.886951ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:23:56Z" - latency: 1.871652ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:22:56Z" - latency: 1.821617ms message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-network-check-target-ip-10-0-128-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "92949" uid: 4df5c198-37ff-4b37-91b1-5a615ae283cf spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:59:56Z" message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029929ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 1.322126ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:29:56Z" - latency: 980.621µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:28:56Z" - latency: 1.37485ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:27:56Z" - latency: 770.628µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:26:56Z" - latency: 2.048014ms message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:25:56Z" - latency: 927.401µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:24:56Z" - latency: 948.017µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:23:56Z" - latency: 810.844µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:22:56Z" - latency: 821.528µs message: 'network-check-target-ip-10-0-128-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-network-check-target-ip-10-0-141-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "92950" uid: d96c91dc-8306-4c3a-8458-f6cddf7e70b9 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T05:59:56Z" message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041755ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 2.167592ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:29:56Z" - latency: 1.728787ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:28:56Z" - latency: 2.082256ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:27:56Z" - latency: 1.804271ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:26:56Z" - latency: 2.05072ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:25:56Z" - latency: 2.192461ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:24:56Z" - latency: 2.012369ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:23:56Z" - latency: 2.011288ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:22:56Z" - latency: 1.949014ms message: 'network-check-target-ip-10-0-141-25: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:52:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-243-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-243.ec2.internal uid: 6ba72cab-ea24-442b-b8ad-50a8a6903568 resourceVersion: "96258" uid: a7a2f06f-db70-45c8-b535-c9e751721ca6 spec: sourcePod: network-check-source-6947749cfc-lxqzc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T05:58:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023814ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:34:56Z" - latency: 2.407768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T07:34:56Z" - latency: 812.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:33:56Z" - latency: 2.018596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T07:33:56Z" - latency: 873.435µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:32:56Z" - latency: 1.751973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T07:32:56Z" - latency: 913.636µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:31:56Z" - latency: 2.116233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T07:31:56Z" - latency: 1.022084ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T07:30:56Z" - latency: 1.969296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T07:30:56Z" kind: List metadata: resourceVersion: ""