apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14365" uid: e66404ee-29bd-48fe-a9be-ccd4f0ca6bc6 spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T14:03:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 979.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:42Z" - latency: 912.016µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 933.786µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 1.21205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 1.066479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 1.348036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 868.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14037" uid: fc298897-df11-4b94-8c9c-dd3508127f49 spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:02:42Z" message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.964605ms message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 7.942861ms message: 'load-balancer-api-external: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:42Z" - latency: 4.503365ms message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 8.370162ms message: 'load-balancer-api-external: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:42Z" - latency: 4.163631ms message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 8.592832ms message: 'load-balancer-api-external: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:42Z" - latency: 3.675327ms message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 8.492026ms message: 'load-balancer-api-external: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:42Z" - latency: 3.711092ms message: 'load-balancer-api-external: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 8.424745ms message: 'load-balancer-api-external: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:58:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14038" uid: 476500cd-a7a0-4e81-8c5f-0d75188a034d spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T14:02:42Z" message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.23589ms message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 8.028189ms message: 'load-balancer-api-internal: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:42Z" - latency: 4.514495ms message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 8.400145ms message: 'load-balancer-api-internal: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:42Z" - latency: 3.504073ms message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 8.539395ms message: 'load-balancer-api-internal: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:42Z" - latency: 3.762975ms message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 8.53366ms message: 'load-balancer-api-internal: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:42Z" - latency: 3.703884ms message: 'load-balancer-api-internal: tcp connection to a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 8.388734ms message: 'load-balancer-api-internal: resolved host name a39c3c5183d4344dda4a0cec473278de-45fa3230b1b0e7ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T13:58:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-134-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14363" uid: 932acc18-20c6-4e10-bcb2-2e5039efbbd6 spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:03:42Z" message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.856896ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:42Z" - latency: 1.675871ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 1.663398ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 1.892822ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 1.591526ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 1.841962ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 1.862473ms message: 'network-check-target-ip-10-0-134-3: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-136-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14362" uid: 614d7c2c-ce3a-4698-a513-de95eadaa31e spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:03:42Z" message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.968µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:42Z" - latency: 895.603µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 852.466µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 1.595122ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 906.263µs message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 1.065592ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 1.623752ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-ip-10-0-141-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14364" uid: 2accf6cd-54e6-47b5-af16-ab24d53cbf12 spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T14:03:42Z" message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.264561ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:03:42Z" - latency: 2.162152ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 2.002414ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 2.208991ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 1.965615ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 5.782068ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 2.402484ms message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:57:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T13:56:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-105-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-105.ec2.internal uid: eeae0fd9-4206-4549-a9a9-3f1308e7b923 resourceVersion: "14036" uid: adc4cd80-659b-4482-a498-7e6f7594f02a spec: sourcePod: network-check-source-7d88cb55d8-xhw54 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T14:02:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.178871ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:02:42Z" - latency: 1.588507ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:02:42Z" - latency: 819.896µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:01:42Z" - latency: 1.719704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:01:42Z" - latency: 999.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T14:00:42Z" - latency: 2.050805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T14:00:42Z" - latency: 754.443µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:59:42Z" - latency: 1.808724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T13:59:42Z" - latency: 988.764µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T13:58:42Z" - latency: 1.832559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T13:58:42Z" kind: List metadata: resourceVersion: ""