apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "69004" uid: a0f211ce-7a81-4bcf-806d-e1c99cb9f7f5 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T07:24:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.206708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:06:57Z" - latency: 1.148853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 1.461148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 1.021497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 1.261431ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 1.239634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 1.234089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:00:57Z" - latency: 1.508578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:59:57Z" - latency: 1.229468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:58:57Z" - latency: 1.093296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "68178" uid: 465a23eb-220a-4956-8e25-312096d31210 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T07:23:57Z" message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.450398ms message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 8.833463ms message: 'load-balancer-api-external: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:05:57Z" - latency: 6.345559ms message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 9.129071ms message: 'load-balancer-api-external: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:04:57Z" - latency: 4.661019ms message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 7.876473ms message: 'load-balancer-api-external: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:03:57Z" - latency: 8.916898ms message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 7.346333ms message: 'load-balancer-api-external: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:02:57Z" - latency: 5.510826ms message: 'load-balancer-api-external: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 6.760316ms message: 'load-balancer-api-external: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:01:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "68179" uid: 19d6db82-ae86-4aea-baaf-53720fc961a3 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T07:23:57Z" message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.419189ms message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 8.867078ms message: 'load-balancer-api-internal: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:05:57Z" - latency: 4.718154ms message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 8.865811ms message: 'load-balancer-api-internal: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:04:57Z" - latency: 3.634744ms message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 7.831746ms message: 'load-balancer-api-internal: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:03:57Z" - latency: 5.058242ms message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 7.055743ms message: 'load-balancer-api-internal: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:02:57Z" - latency: 4.480057ms message: 'load-balancer-api-internal: tcp connection to ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 6.825218ms message: 'load-balancer-api-internal: resolved host name ac2fbc5719346468f85f9c7a856b1aee-978c3911c174d306.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T08:01:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-136-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "69001" uid: fd7ea114-4679-4ad5-8bc3-6297d99c78d8 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T07:24:57Z" message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.425µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:06:57Z" - latency: 1.659996ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 1.831631ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 917.811µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 1.150306ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 1.153944ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 944.748µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:00:57Z" - latency: 1.65937ms message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:59:57Z" - latency: 954.334µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:58:57Z" - latency: 921.439µs message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-137-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "69002" uid: bf7a9ff2-58bc-4428-a7dc-0912bb076074 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T07:24:57Z" message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.271049ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:06:57Z" - latency: 2.030878ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 2.040314ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 2.229293ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 2.111449ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 1.815569ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 1.932066ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:00:57Z" - latency: 1.974256ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:59:57Z" - latency: 1.954008ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:58:57Z" - latency: 2.063231ms message: 'network-check-target-ip-10-0-137-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-ip-10-0-143-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "69003" uid: 2169f154-cf0d-4982-aab0-6583df7417c8 spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T07:24:57Z" message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.500824ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:06:57Z" - latency: 2.523431ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 2.728681ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 2.332017ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 2.420919ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 2.45679ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 2.220333ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:00:57Z" - latency: 2.132726ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:59:57Z" - latency: 2.345198ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:58:57Z" - latency: 2.440287ms message: 'network-check-target-ip-10-0-143-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T07:57:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T07:17:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-73.ec2.internal uid: f499c951-319e-4765-b69d-2c47d98da97f resourceVersion: "68177" uid: 23393bb4-bf6b-471f-892c-e84c93c4342e spec: sourcePod: network-check-source-7d88cb55d8-xxk99 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T07:23:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.25µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:05:57Z" - latency: 2.081374ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T08:05:57Z" - latency: 1.223082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:04:57Z" - latency: 1.793458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T08:04:57Z" - latency: 928.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:03:57Z" - latency: 1.786559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T08:03:57Z" - latency: 1.035012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:02:57Z" - latency: 1.793921ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T08:02:57Z" - latency: 886.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T08:01:57Z" - latency: 1.784988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T08:01:57Z" kind: List metadata: resourceVersion: ""