apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "37623" uid: d8857635-66be-4046-8953-a6ffd7b7dd66 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T17:14:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 1.352913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 848.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 840.069µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:32:43Z" - latency: 1.040777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:31:43Z" - latency: 939.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:30:43Z" - latency: 1.169268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:29:43Z" - latency: 1.062839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:28:43Z" - latency: 993.091µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:27:43Z" - latency: 1.57129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:26:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "39719" uid: 8e4bec73-d92d-444f-ac12-a45d6f1311b7 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T17:13:43Z" message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.240032ms message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:37:43Z" - latency: 6.192214ms message: 'load-balancer-api-external: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:37:43Z" - latency: 3.738562ms message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:36:43Z" - latency: 6.960747ms message: 'load-balancer-api-external: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:36:43Z" - latency: 3.782767ms message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 7.384649ms message: 'load-balancer-api-external: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:35:43Z" - latency: 6.649083ms message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 8.206946ms message: 'load-balancer-api-external: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:34:43Z" - latency: 5.220384ms message: 'load-balancer-api-external: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 6.582961ms message: 'load-balancer-api-external: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "39720" uid: a056ffd9-ba9a-4ffc-9e4f-63ea3c5d9e51 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T17:13:43Z" message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.017083ms message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:37:43Z" - latency: 6.059623ms message: 'load-balancer-api-internal: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:37:43Z" - latency: 3.742186ms message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:36:43Z" - latency: 6.872491ms message: 'load-balancer-api-internal: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:36:43Z" - latency: 6.318387ms message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 7.327963ms message: 'load-balancer-api-internal: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:35:43Z" - latency: 6.652664ms message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 8.047102ms message: 'load-balancer-api-internal: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:34:43Z" - latency: 4.876991ms message: 'load-balancer-api-internal: tcp connection to a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 6.483447ms message: 'load-balancer-api-internal: resolved host name a3f1496cd9c1f40679bc178130bd4495-1821e9fbf9429ecc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T17:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-network-check-target-ip-10-0-131-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "37620" uid: 9e7c2021-f03c-4fb8-91ea-f263b42edaf6 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T17:14:43Z" message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105806ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 2.18993ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 2.055154ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 2.285291ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:32:43Z" - latency: 2.297707ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:31:43Z" - latency: 2.16671ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:30:43Z" - latency: 2.400424ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:29:43Z" - latency: 1.787099ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:28:43Z" - latency: 2.14588ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:27:43Z" - latency: 2.407432ms message: 'network-check-target-ip-10-0-131-143: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:26:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-network-check-target-ip-10-0-135-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "37621" uid: 246f3828-bfb2-49a2-befa-dcee045a2930 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T17:14:43Z" message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.405501ms message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 929.477µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 1.002247ms message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 1.351179ms message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:32:43Z" - latency: 936.496µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:31:43Z" - latency: 1.373474ms message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:30:43Z" - latency: 952.828µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:29:43Z" - latency: 862.74µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:28:43Z" - latency: 869.731µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:27:43Z" - latency: 943.342µs message: 'network-check-target-ip-10-0-135-136: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:26:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-network-check-target-ip-10-0-136-67 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "37622" uid: 78b6d4e2-48fc-4652-be23-dd90df2a62a5 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T17:14:43Z" message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.289546ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 2.380703ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 2.199795ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 2.698332ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:32:43Z" - latency: 2.681522ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:31:43Z" - latency: 2.681486ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:30:43Z" - latency: 2.376611ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:29:43Z" - latency: 2.174588ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:28:43Z" - latency: 2.313715ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:27:43Z" - latency: 2.028952ms message: 'network-check-target-ip-10-0-136-67: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:26:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T17:07:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-136-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-136.ec2.internal uid: 6aa46aef-ddb7-41fe-88f2-545a4cfa04f0 resourceVersion: "39718" uid: a2c0ecf4-8607-49c3-ba30-55df707366e5 spec: sourcePod: network-check-source-7f44b6dd87-q284l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T17:13:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:37:43Z" - latency: 1.616562ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T17:37:43Z" - latency: 1.181124ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:36:43Z" - latency: 1.879165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T17:36:43Z" - latency: 913.194µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:35:43Z" - latency: 1.819772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T17:35:43Z" - latency: 759.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:34:43Z" - latency: 2.075471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T17:34:43Z" - latency: 834.891µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T17:33:43Z" - latency: 1.648698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T17:33:43Z" kind: List metadata: resourceVersion: ""