apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61303" uid: a2f65163-b92c-4fa8-8f90-3a2d1d1ca676 spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T20:51:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 999.301µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 902.972µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 1.241489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 990µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 1.41272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 1.14421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:21:13Z" - latency: 1.030682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:20:13Z" - latency: 1.147073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:19:13Z" - latency: 808.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:18:13Z" - latency: 1.067954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61305" uid: dae39021-0679-4af2-b13a-4766ff334358 spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:50:13Z" message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.476288ms message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 7.039825ms message: 'load-balancer-api-external: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:26:13Z" - latency: 5.03268ms message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 6.263738ms message: 'load-balancer-api-external: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:25:13Z" - latency: 4.631551ms message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 6.942744ms message: 'load-balancer-api-external: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:24:13Z" - latency: 4.364595ms message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 7.815294ms message: 'load-balancer-api-external: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:23:13Z" - latency: 5.264581ms message: 'load-balancer-api-external: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 7.327933ms message: 'load-balancer-api-external: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:22:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61304" uid: 41be53fc-949d-4570-b5c6-2cf56cd94b4a spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T20:50:13Z" message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.513749ms message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 6.996768ms message: 'load-balancer-api-internal: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:26:13Z" - latency: 5.044666ms message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 6.242798ms message: 'load-balancer-api-internal: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:25:13Z" - latency: 4.431896ms message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 7.022018ms message: 'load-balancer-api-internal: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:24:13Z" - latency: 4.200571ms message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 7.871721ms message: 'load-balancer-api-internal: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:23:13Z" - latency: 5.243366ms message: 'load-balancer-api-internal: tcp connection to ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 7.303701ms message: 'load-balancer-api-internal: resolved host name ab0c6c207b13b4c4f8b66dd5f3149082-a561a320a8071240.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:22:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-network-check-target-ip-10-0-136-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61299" uid: 76a50767-1583-45cd-ba74-06dfd182b9bc spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:51:13Z" message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.193µs message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 1.048948ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 1.3371ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 946.598µs message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 1.271936ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 831.624µs message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:21:13Z" - latency: 1.17697ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:20:13Z" - latency: 1.207729ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:19:13Z" - latency: 1.388072ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:18:13Z" - latency: 801.059µs message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-network-check-target-ip-10-0-141-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61300" uid: 340c093d-d148-4b47-abcf-bddbb2c90611 spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:51:13Z" message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299925ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 2.239314ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 2.421554ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 2.516391ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 2.417796ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 2.198488ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:21:13Z" - latency: 2.306488ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:20:13Z" - latency: 2.175236ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:19:13Z" - latency: 2.245331ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:18:13Z" - latency: 1.97946ms message: 'network-check-target-ip-10-0-141-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-network-check-target-ip-10-0-142-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61302" uid: 2de53ce7-b471-4da2-8271-a21c967fd2e5 spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T20:51:13Z" message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.325468ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 2.361823ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 2.49743ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 2.596736ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 2.375119ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 2.095516ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:21:13Z" - latency: 2.347784ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:20:13Z" - latency: 2.279784ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:19:13Z" - latency: 2.193035ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:18:13Z" - latency: 2.304281ms message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T20:44:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-104.ec2.internal uid: ed3db8f8-b713-4879-b632-b4fad345d01c resourceVersion: "61301" uid: 7e82a1da-79cd-4a47-a601-aba5142ee998 spec: sourcePod: network-check-source-869dcfcdcd-m6dlf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T20:50:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154415ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:13Z" - latency: 1.637949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:26:13Z" - latency: 823.389µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:25:13Z" - latency: 1.520179ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:25:13Z" - latency: 1.059923ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:24:13Z" - latency: 1.781366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:24:13Z" - latency: 1.043351ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:23:13Z" - latency: 2.014917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:23:13Z" - latency: 1.014718ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:22:13Z" - latency: 1.817066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:22:13Z" kind: List metadata: resourceVersion: ""