apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "30596" uid: f838dd2b-d99d-437c-9abb-5add313d36dd spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:31:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.917549ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:31Z" - latency: 971.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:31Z" - latency: 984.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 1.006735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 1.063133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 922.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 1.203148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 1.533265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:31:31Z" - latency: 1.116843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:31Z" - latency: 1.431883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "29335" uid: 2a84e45e-cb94-48fb-af53-246104007b07 spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:30:31Z" message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.289415ms message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 12.693406ms message: 'load-balancer-api-external: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:31Z" - latency: 5.326516ms message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 8.143101ms message: 'load-balancer-api-external: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:31Z" - latency: 5.285133ms message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 10.526403ms message: 'load-balancer-api-external: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:31Z" - latency: 6.382988ms message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 8.700869ms message: 'load-balancer-api-external: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:33:31Z" - latency: 5.244391ms message: 'load-balancer-api-external: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 10.797912ms message: 'load-balancer-api-external: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "29336" uid: fa7bb9b8-3036-412d-8ec5-77bd3bad93dd spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:30:31Z" message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.696303ms message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 12.660668ms message: 'load-balancer-api-internal: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:31Z" - latency: 5.829846ms message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 8.078345ms message: 'load-balancer-api-internal: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:31Z" - latency: 5.279773ms message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 10.499656ms message: 'load-balancer-api-internal: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:31Z" - latency: 6.404762ms message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 8.656219ms message: 'load-balancer-api-internal: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:33:31Z" - latency: 5.193641ms message: 'load-balancer-api-internal: tcp connection to af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 10.724865ms message: 'load-balancer-api-internal: resolved host name af161596e866a42c3a3108de6ba9748c-a2a5f07ecd26a4f8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-network-check-target-ip-10-0-133-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "30594" uid: 4bd16f65-b21a-4446-b5af-982fe1e5510a spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:31:31Z" message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.209041ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:31Z" - latency: 1.860252ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:31Z" - latency: 2.230769ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 1.858557ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 2.185291ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 2.010499ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 2.066832ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 2.111217ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:31:31Z" - latency: 2.434734ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:31Z" - latency: 1.966485ms message: 'network-check-target-ip-10-0-133-2: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-network-check-target-ip-10-0-134-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "30595" uid: b0161241-ed01-4e5f-aeff-d6b44b195e82 spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:31:31Z" message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222268ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:31Z" - latency: 2.597428ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:31Z" - latency: 2.314883ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 2.045294ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 2.227712ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 2.158733ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 2.529372ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 2.121837ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:31:31Z" - latency: 2.221375ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:31Z" - latency: 2.222195ms message: 'network-check-target-ip-10-0-134-99: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-network-check-target-ip-10-0-138-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "30593" uid: 450234aa-2cde-4f96-9486-a631decdd0d5 spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:31:31Z" message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.11944ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:31Z" - latency: 878.134µs message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:31Z" - latency: 1.327405ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 881.375µs message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 2.834339ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 936.257µs message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 1.300609ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 2.64661ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:31:31Z" - latency: 1.166376ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:31Z" - latency: 1.23643ms message: 'network-check-target-ip-10-0-138-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:24:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-245-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-245.ec2.internal uid: 2c3cc68c-f55b-480a-8229-5eb20660c094 resourceVersion: "29334" uid: fcd82244-38ce-461f-a012-90a3acfc12a9 spec: sourcePod: network-check-source-dbd9cf844-75w7t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:30:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.130568ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:31Z" - latency: 1.90582ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:31Z" - latency: 912.562µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:31Z" - latency: 1.820222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:31Z" - latency: 873.888µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:31Z" - latency: 2.760252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:31Z" - latency: 1.024463ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:33:31Z" - latency: 1.889736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:33:31Z" - latency: 1.045374ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:32:31Z" - latency: 1.845653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:32:31Z" kind: List metadata: resourceVersion: ""