apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63538" uid: 062804a5-ec49-4d26-82fe-7acffbd6d67f spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T04:43:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.785923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 788.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 1.012251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 1.162746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 820.558µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 986.644µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:15Z" - latency: 799.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:15Z" - latency: 1.075865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:15Z" - latency: 1.007239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:15Z" - latency: 1.18023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63539" uid: d16910a9-5c03-47cb-a851-3567ed167871 spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T04:42:15Z" message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.202819ms message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 10.228487ms message: 'load-balancer-api-external: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:18:15Z" - latency: 4.586502ms message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 8.55772ms message: 'load-balancer-api-external: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:17:15Z" - latency: 4.940128ms message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 8.076179ms message: 'load-balancer-api-external: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:16:15Z" - latency: 5.476195ms message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 8.563618ms message: 'load-balancer-api-external: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:15:15Z" - latency: 5.193047ms message: 'load-balancer-api-external: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 8.786799ms message: 'load-balancer-api-external: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63540" uid: f8744302-5188-4f94-8e45-58d8da0bf64e spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T04:42:15Z" message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.193248ms message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 10.269157ms message: 'load-balancer-api-internal: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:18:15Z" - latency: 4.484289ms message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 8.63656ms message: 'load-balancer-api-internal: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:17:15Z" - latency: 3.476152ms message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 8.165331ms message: 'load-balancer-api-internal: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:16:15Z" - latency: 5.478546ms message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 8.520646ms message: 'load-balancer-api-internal: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:15:15Z" - latency: 5.201335ms message: 'load-balancer-api-internal: tcp connection to a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 8.843888ms message: 'load-balancer-api-internal: resolved host name a1a0c0c9344824100812ab3839202436-126481b8a9c029f3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-network-check-target-ip-10-0-133-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63536" uid: 0e4aab3d-84b4-4ddc-8805-e609cd7130e8 spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:43:15Z" message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.434698ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 2.595522ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 2.362313ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 2.086211ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 1.618287ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 2.388644ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:15Z" - latency: 2.083706ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:15Z" - latency: 2.361126ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:15Z" - latency: 2.32041ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:15Z" - latency: 1.967925ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-network-check-target-ip-10-0-137-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63535" uid: 6b153bfe-7515-4cb1-a4db-1d42e1d782d9 spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:43:15Z" message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.979854ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 1.992113ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 1.978456ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 1.860857ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 1.577678ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 1.843052ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:15Z" - latency: 1.751009ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:15Z" - latency: 1.935378ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:15Z" - latency: 2.09183ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:15Z" - latency: 1.738125ms message: 'network-check-target-ip-10-0-137-249: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-network-check-target-ip-10-0-142-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63534" uid: e5402bc2-f7c4-4839-9a14-7a76ef088e3f spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T04:43:15Z" message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.656µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 826.262µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 866.19µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 765.546µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 709.93µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 970.622µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:13:15Z" - latency: 808.733µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:12:15Z" - latency: 810.877µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:11:15Z" - latency: 957.041µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:10:15Z" - latency: 742.025µs message: 'network-check-target-ip-10-0-142-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:09:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T04:36:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-47.ec2.internal uid: eec2467e-a63b-4916-84c1-3b6ec725a6c3 resourceVersion: "63537" uid: 57f2f176-6fd4-4cbf-a70e-9b20c298bea0 spec: sourcePod: network-check-source-7bc5b6bf85-mmslh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T04:42:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.131712ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:18:15Z" - latency: 2.370051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:18:15Z" - latency: 1.039012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:17:15Z" - latency: 1.668477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:17:15Z" - latency: 854.3µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:16:15Z" - latency: 1.69912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:16:15Z" - latency: 1.165556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:15:15Z" - latency: 1.58476ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:15:15Z" - latency: 762.803µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T05:14:15Z" - latency: 2.10467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T05:14:15Z" kind: List metadata: resourceVersion: ""