apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "44139" uid: 9cdc8da1-ff58-490b-8253-5bd42d8c34dc spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T13:23:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.33464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:44:05Z" - latency: 1.166766ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:43:05Z" - latency: 814.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:42:05Z" - latency: 1.189365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:41:05Z" - latency: 1.208081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 1.045478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 980.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 1.101287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 1.296501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 871.191µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "40006" uid: e4bf206e-3191-47d4-bf65-131fc75ae6bc spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T13:22:05Z" message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.107844ms message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 7.307736ms message: 'load-balancer-api-external: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:40:05Z" - latency: 4.408449ms message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 6.373493ms message: 'load-balancer-api-external: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:39:05Z" - latency: 4.270999ms message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 6.112841ms message: 'load-balancer-api-external: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:38:05Z" - latency: 4.453188ms message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 6.724861ms message: 'load-balancer-api-external: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:37:05Z" - latency: 4.894084ms message: 'load-balancer-api-external: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 6.489896ms message: 'load-balancer-api-external: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:36:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "40005" uid: 6105efa9-6c7e-4173-8d90-8943a36f7217 spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T13:22:05Z" message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.116265ms message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 7.263044ms message: 'load-balancer-api-internal: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:40:05Z" - latency: 4.370088ms message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 6.463389ms message: 'load-balancer-api-internal: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:39:05Z" - latency: 4.025426ms message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 6.037231ms message: 'load-balancer-api-internal: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:38:05Z" - latency: 4.004301ms message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 6.840112ms message: 'load-balancer-api-internal: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:37:05Z" - latency: 4.298574ms message: 'load-balancer-api-internal: tcp connection to a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 6.445645ms message: 'load-balancer-api-internal: resolved host name a10e879bb80274f1eadca2fdac7e94b0-095afbdc99da6ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T13:36:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-network-check-target-ip-10-0-137-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "44138" uid: d141701a-c7ba-4603-a89f-6e26e6f5bca0 spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T13:23:05Z" message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.708233ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:44:05Z" - latency: 2.376272ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:43:05Z" - latency: 1.915007ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:42:05Z" - latency: 2.184614ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:41:05Z" - latency: 2.289605ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 2.234667ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 2.215397ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 2.512522ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 2.133808ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 2.576309ms message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-network-check-target-ip-10-0-141-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "44136" uid: 97f1e8db-c143-4326-a014-ba059880a6d9 spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T13:23:05Z" message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.197µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:44:05Z" - latency: 942.534µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:43:05Z" - latency: 776.789µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:42:05Z" - latency: 905.697µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:41:05Z" - latency: 1.220413ms message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 852.347µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 909.12µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 840.806µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 904.337µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 918.348µs message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-network-check-target-ip-10-0-142-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "44137" uid: aece308a-981c-4728-a7c0-133fe1e918c0 spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T13:23:05Z" message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.084752ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:44:05Z" - latency: 2.008499ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:43:05Z" - latency: 2.044227ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:42:05Z" - latency: 2.21649ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:41:05Z" - latency: 2.252537ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 2.301212ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 2.361173ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 2.441908ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 2.267831ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 2.214963ms message: 'network-check-target-ip-10-0-142-166: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T13:16:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-234.ec2.internal uid: 28ce692a-273a-4dd1-93a9-194d5e9f28e9 resourceVersion: "40004" uid: 8e62dabc-c89b-4136-8248-7a723ac42adc spec: sourcePod: network-check-source-7b678d77c7-vjtz5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T13:22:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15859ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:40:05Z" - latency: 1.640961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T13:40:05Z" - latency: 872.393µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:39:05Z" - latency: 1.654612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T13:39:05Z" - latency: 1.105109ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:38:05Z" - latency: 1.791371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T13:38:05Z" - latency: 811.843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:37:05Z" - latency: 2.012827ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T13:37:05Z" - latency: 886.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T13:36:05Z" - latency: 1.577829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T13:36:05Z" kind: List metadata: resourceVersion: ""