apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "55468" uid: 5d8fe0a9-a754-44ff-8d69-3193fa1cb66f spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:02:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 834.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 1.427612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 1.165853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 1.108417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:26:27Z" - latency: 957.972µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:25:27Z" - latency: 1.078981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:24:27Z" - latency: 869.381µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:23:27Z" - latency: 828.26µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:22:27Z" - latency: 969.25µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "56337" uid: a98018f3-20f2-4e85-95b9-694093020fbf spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:01:27Z" message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.661638ms message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:31:27Z" - latency: 6.910033ms message: 'load-balancer-api-external: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:31:27Z" - latency: 3.395003ms message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 7.704141ms message: 'load-balancer-api-external: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:30:27Z" - latency: 3.651483ms message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 7.241013ms message: 'load-balancer-api-external: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:29:27Z" - latency: 5.162354ms message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 7.652842ms message: 'load-balancer-api-external: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:28:27Z" - latency: 9.011812ms message: 'load-balancer-api-external: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 6.869571ms message: 'load-balancer-api-external: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "56338" uid: 3bb017da-b65e-4440-8bd8-5e47123e8901 spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:01:27Z" message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.960512ms message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:31:27Z" - latency: 6.989665ms message: 'load-balancer-api-internal: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:31:27Z" - latency: 4.995091ms message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 7.743752ms message: 'load-balancer-api-internal: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:30:27Z" - latency: 3.640223ms message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 7.271043ms message: 'load-balancer-api-internal: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:29:27Z" - latency: 5.159443ms message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 7.732565ms message: 'load-balancer-api-internal: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:28:27Z" - latency: 9.040963ms message: 'load-balancer-api-internal: tcp connection to a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 6.929549ms message: 'load-balancer-api-internal: resolved host name a10b599e408b04beeb75964312fedefb-0b44023226f80b0e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:27:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-128-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "55465" uid: f1200fa8-8b4c-4d1c-a8c1-f633b0206ea2 spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:02:27Z" message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.012µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 1.293411ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 897.185µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 1.473118ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 763.911µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:26:27Z" - latency: 877.453µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:25:27Z" - latency: 1.348439ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:24:27Z" - latency: 995.745µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:23:27Z" - latency: 916.848µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:22:27Z" - latency: 885.751µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-133-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "55466" uid: dbaaca87-43e9-45ee-af2d-90da72bbf1ba spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:02:27Z" message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266165ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 1.881896ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 1.912853ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 2.079449ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 2.283984ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:26:27Z" - latency: 1.992027ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:25:27Z" - latency: 2.017906ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:24:27Z" - latency: 2.005699ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:23:27Z" - latency: 1.647169ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:22:27Z" - latency: 1.957018ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-136-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "55467" uid: bfcc4a04-ea77-4828-bbef-33e496097982 spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:02:27Z" message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.311963ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 2.00351ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 2.293771ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 2.206066ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 2.144201ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:26:27Z" - latency: 2.160973ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:25:27Z" - latency: 2.311587ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:24:27Z" - latency: 2.283642ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:23:27Z" - latency: 2.085501ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:22:27Z" - latency: 2.373939ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T16:55:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.ec2.internal uid: 89dd087d-8c94-4a30-b9fe-f369e5b16dcb resourceVersion: "56336" uid: 63330a85-ad76-48cf-8e13-bb28b23e8858 spec: sourcePod: network-check-source-869dcfcdcd-lbhfp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:01:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.578µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:31:27Z" - latency: 2.287491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:31:27Z" - latency: 1.073721ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:30:27Z" - latency: 2.102723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:30:27Z" - latency: 922.308µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:29:27Z" - latency: 2.034826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:29:27Z" - latency: 963.756µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:28:27Z" - latency: 1.928596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:28:27Z" - latency: 1.123654ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:27:27Z" - latency: 1.811021ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:27:27Z" kind: List metadata: resourceVersion: ""