apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "43909" uid: 2c3d32e2-3657-42c3-80a0-3a344100dfcd spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T14:02:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:58:47Z" - latency: 1.135466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:57:47Z" - latency: 1.162944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:56:47Z" - latency: 961.654µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 792.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 1.080928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 884.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 1.176827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 1.056657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:50:47Z" - latency: 1.206546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "42048" uid: 5d949162-cf30-4a27-82a2-81f790b20617 spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:01:47Z" message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.844622ms message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 8.005703ms message: 'load-balancer-api-external: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:55:47Z" - latency: 4.736647ms message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 8.174316ms message: 'load-balancer-api-external: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:54:47Z" - latency: 4.889605ms message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 8.754271ms message: 'load-balancer-api-external: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:53:47Z" - latency: 3.590846ms message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 8.885565ms message: 'load-balancer-api-external: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:52:47Z" - latency: 4.299853ms message: 'load-balancer-api-external: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 8.560766ms message: 'load-balancer-api-external: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:51:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "42047" uid: 14720429-287f-4d54-a0d6-a36815b063f7 spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:01:47Z" message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.529201ms message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 7.907422ms message: 'load-balancer-api-internal: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:55:47Z" - latency: 4.707978ms message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 8.205296ms message: 'load-balancer-api-internal: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:54:47Z" - latency: 4.945567ms message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 8.691459ms message: 'load-balancer-api-internal: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:53:47Z" - latency: 3.821629ms message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 8.851721ms message: 'load-balancer-api-internal: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:52:47Z" - latency: 4.295726ms message: 'load-balancer-api-internal: tcp connection to af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 8.595184ms message: 'load-balancer-api-internal: resolved host name af4df00675e6047b395db49dac2cc364-cd75ac46da1bd940.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:51:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-130-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "43908" uid: d2a3a13a-32c3-4c7e-add2-797eda693782 spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:02:47Z" message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.281424ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:58:47Z" - latency: 2.139293ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:57:47Z" - latency: 2.300633ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:56:47Z" - latency: 2.311115ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 2.295457ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 2.311661ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 2.73302ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 2.385883ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 2.135133ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:50:47Z" - latency: 2.517941ms message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-132-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "43907" uid: ff5bca73-8a08-4c62-a3a1-94395ce2debf spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:02:47Z" message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.93586ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:58:47Z" - latency: 2.23364ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:57:47Z" - latency: 1.892568ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:56:47Z" - latency: 1.73953ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 1.929507ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 2.382655ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 1.946595ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 2.117984ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 2.144838ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:50:47Z" - latency: 2.202953ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-139-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "43906" uid: 3b7f8e32-db8b-46ae-9724-33d7b873787d spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:02:47Z" message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.283179ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:58:47Z" - latency: 872.919µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:57:47Z" - latency: 833.597µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:56:47Z" - latency: 844.73µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 694.183µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 810.168µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 706.193µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 810.366µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 1.332003ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:50:47Z" - latency: 1.026428ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:55:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: f8746aa6-bdf1-4209-a344-0c8e1a3b67db resourceVersion: "42046" uid: d189fe7a-bc31-4b54-a722-bb8292aec5b1 spec: sourcePod: network-check-source-7f44b6dd87-tz48w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T14:01:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.060381ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:55:47Z" - latency: 1.745837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:55:47Z" - latency: 770.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:54:47Z" - latency: 1.620191ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:54:47Z" - latency: 946.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:53:47Z" - latency: 1.770732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:53:47Z" - latency: 760.381µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:52:47Z" - latency: 1.599585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:52:47Z" - latency: 820.535µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:51:47Z" - latency: 1.709796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:51:47Z" kind: List metadata: resourceVersion: ""