apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "56296" uid: 3002f2f4-6fba-4c70-bceb-eb13db53bf54 spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T01:31:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:59:23Z" - latency: 1.737044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:58:23Z" - latency: 1.179025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:57:23Z" - latency: 1.192007ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:56:23Z" - latency: 1.020599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:55:23Z" - latency: 979.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 1.422409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 888.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 1.032357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 976.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "51390" uid: e10b3362-80f9-4ff0-acd3-f3c03aaf95f6 spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T01:30:23Z" message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.705252ms message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 7.112866ms message: 'load-balancer-api-external: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:54:23Z" - latency: 4.000966ms message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 6.772492ms message: 'load-balancer-api-external: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:53:23Z" - latency: 4.792194ms message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 8.305487ms message: 'load-balancer-api-external: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:52:23Z" - latency: 3.806845ms message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 6.716909ms message: 'load-balancer-api-external: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:51:23Z" - latency: 3.975514ms message: 'load-balancer-api-external: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - latency: 6.839627ms message: 'load-balancer-api-external: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "51391" uid: 91c18eaa-93b2-4a91-ab97-3ebd7bd3c682 spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T01:30:23Z" message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.412055ms message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 7.318775ms message: 'load-balancer-api-internal: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:54:23Z" - latency: 4.022313ms message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 6.855188ms message: 'load-balancer-api-internal: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:53:23Z" - latency: 4.764837ms message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 8.339989ms message: 'load-balancer-api-internal: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:52:23Z" - latency: 3.539682ms message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 6.79881ms message: 'load-balancer-api-internal: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:51:23Z" - latency: 3.399869ms message: 'load-balancer-api-internal: tcp connection to a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - latency: 6.752417ms message: 'load-balancer-api-internal: resolved host name a361b39749005419eba4e054ebdfef06-07828547b89485bd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-133-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "56293" uid: 6bffae40-a5bb-4951-bdac-38c686068ede spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:31:23Z" message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040456ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:59:23Z" - latency: 2.158162ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:58:23Z" - latency: 1.206582ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:57:23Z" - latency: 888.121µs message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:56:23Z" - latency: 1.006851ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:55:23Z" - latency: 804.932µs message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 1.026565ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 1.598841ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 930.447µs message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 1.0616ms message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-134-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "56295" uid: 70447c3d-1234-4694-bf7c-63a68ab1323a spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:31:23Z" message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.209271ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:59:23Z" - latency: 2.154751ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:58:23Z" - latency: 2.213177ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:57:23Z" - latency: 2.203118ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:56:23Z" - latency: 1.799973ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:55:23Z" - latency: 2.020742ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 2.446951ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 2.274584ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 2.140179ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 2.002538ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-143-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "56294" uid: cfc8165f-0707-445e-a422-d10400a3217c spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:31:23Z" message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039564ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:59:23Z" - latency: 1.86164ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:58:23Z" - latency: 2.068305ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:57:23Z" - latency: 2.136655ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:56:23Z" - latency: 1.759328ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:55:23Z" - latency: 1.760193ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 2.134314ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 1.858889ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 1.988111ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 1.622237ms message: 'network-check-target-ip-10-0-143-159: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:24:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-137-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-137.ec2.internal uid: c342d769-3501-460a-9efd-9758e204f36a resourceVersion: "51389" uid: 45bc0e9c-d301-418f-8a66-909857bdbc83 spec: sourcePod: network-check-source-989f8b8dc-7qs55 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T01:30:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 835.649µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:54:23Z" - latency: 1.921339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:54:23Z" - latency: 828.081µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:53:23Z" - latency: 1.833535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:53:23Z" - latency: 885.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:52:23Z" - latency: 2.523164ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:52:23Z" - latency: 901.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:51:23Z" - latency: 1.572755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:51:23Z" - latency: 871.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:50:23Z" - latency: 1.897264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:50:23Z" kind: List metadata: resourceVersion: ""