apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "56171" uid: aee474ef-5364-4c4c-b5ff-1db5194ae73a spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T09:06:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.069134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 1.17936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 1.032696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 852.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 966.633µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:30:29Z" - latency: 928.747µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:29:29Z" - latency: 868.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:28:29Z" - latency: 1.007778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:27:29Z" - latency: 979.967µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:26:29Z" - latency: 843.118µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:25:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "57251" uid: 49fdb763-2935-48b8-822b-2bd716656bc8 spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T09:05:29Z" message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.034487ms message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:35:29Z" - latency: 9.623465ms message: 'load-balancer-api-external: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:35:29Z" - latency: 4.783013ms message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 8.941119ms message: 'load-balancer-api-external: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:34:29Z" - latency: 4.495716ms message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 9.177975ms message: 'load-balancer-api-external: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:33:29Z" - latency: 3.872724ms message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 13.665619ms message: 'load-balancer-api-external: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:32:29Z" - latency: 5.027071ms message: 'load-balancer-api-external: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 9.428171ms message: 'load-balancer-api-external: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:31:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "57250" uid: 64daa34e-8a22-423f-aa5f-bf82b39a7109 spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T09:05:29Z" message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.471123ms message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:35:29Z" - latency: 9.642214ms message: 'load-balancer-api-internal: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:35:29Z" - latency: 4.788277ms message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 8.878274ms message: 'load-balancer-api-internal: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:34:29Z" - latency: 4.577954ms message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 9.092362ms message: 'load-balancer-api-internal: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:33:29Z" - latency: 4.84615ms message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 13.625523ms message: 'load-balancer-api-internal: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:32:29Z" - latency: 3.831256ms message: 'load-balancer-api-internal: tcp connection to aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 9.462074ms message: 'load-balancer-api-internal: resolved host name aadf5eb8b306f41399a5ebff97ebb5cb-67c66823bcf5a64d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:31:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-network-check-target-ip-10-0-128-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "56169" uid: b7a516b1-d2eb-4456-979d-cbc84779f21f spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:06:29Z" message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.608524ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 2.123945ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 2.336113ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 2.555662ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 2.29702ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:30:29Z" - latency: 2.39734ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:29:29Z" - latency: 2.076613ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:28:29Z" - latency: 2.269475ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:27:29Z" - latency: 2.379961ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:26:29Z" - latency: 1.933514ms message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:25:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-network-check-target-ip-10-0-135-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "56170" uid: 12267ef3-34ab-4b81-99f6-0e12f89d44e0 spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:06:29Z" message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.852098ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 2.217438ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 2.615731ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 2.26177ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 2.403018ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:30:29Z" - latency: 2.501263ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:29:29Z" - latency: 2.699075ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:28:29Z" - latency: 2.839388ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:27:29Z" - latency: 2.41688ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:26:29Z" - latency: 2.906985ms message: 'network-check-target-ip-10-0-135-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:25:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-network-check-target-ip-10-0-140-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "56168" uid: b0100bb5-334b-42e3-b95b-76d8a6f51bbe spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:06:29Z" message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 992.764µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 892.987µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 916.268µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 916.043µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 1.022411ms message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:30:29Z" - latency: 678.686µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:29:29Z" - latency: 833.345µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:28:29Z" - latency: 1.316981ms message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:27:29Z" - latency: 825.789µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:26:29Z" - latency: 878.941µs message: 'network-check-target-ip-10-0-140-31: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:25:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T08:59:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-31-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-31.ec2.internal uid: dc41edb6-c36a-4937-886a-cd8a316fb122 resourceVersion: "57249" uid: 226e4bc4-035e-4bfd-a02a-7b99b8ad4ff6 spec: sourcePod: network-check-source-869dcfcdcd-7lvrl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T09:05:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.03µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:35:29Z" - latency: 2.146443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:35:29Z" - latency: 923.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:34:29Z" - latency: 1.883269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:34:29Z" - latency: 914.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:33:29Z" - latency: 2.002109ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:33:29Z" - latency: 1.003284ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:32:29Z" - latency: 1.811028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:32:29Z" - latency: 884.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:31:29Z" - latency: 1.797233ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:31:29Z" kind: List metadata: resourceVersion: ""