apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "33435" uid: 7cf26d35-ab8e-4a32-9fff-7326f2d51cee spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T20:07:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 2.085083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 1.579233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:19:46Z" - latency: 2.017312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:18:46Z" - latency: 1.118022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:17:46Z" - latency: 1.005891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:16:46Z" - latency: 854.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:15:46Z" - latency: 1.083518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:46Z" - latency: 913.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:46Z" - latency: 1.306068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "35748" uid: 0adcd5f9-2757-40fa-b325-08753e4665e8 spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:06:46Z" message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.309667ms message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:24:46Z" - latency: 6.956ms message: 'load-balancer-api-external: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:24:46Z" - latency: 4.826475ms message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:23:46Z" - latency: 9.004689ms message: 'load-balancer-api-external: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:23:46Z" - latency: 4.494856ms message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:22:46Z" - latency: 6.857866ms message: 'load-balancer-api-external: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:22:46Z" - latency: 4.701305ms message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 8.731598ms message: 'load-balancer-api-external: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:21:46Z" - latency: 5.419798ms message: 'load-balancer-api-external: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 7.619022ms message: 'load-balancer-api-external: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:20:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "35747" uid: c0b60e20-a25f-4d58-9374-a67e817a6b66 spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T20:06:46Z" message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.2977ms message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:24:46Z" - latency: 6.928497ms message: 'load-balancer-api-internal: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:24:46Z" - latency: 4.847649ms message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:23:46Z" - latency: 9.108855ms message: 'load-balancer-api-internal: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:23:46Z" - latency: 4.495434ms message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:22:46Z" - latency: 6.760769ms message: 'load-balancer-api-internal: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:22:46Z" - latency: 4.692684ms message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 8.839206ms message: 'load-balancer-api-internal: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:21:46Z" - latency: 4.33097ms message: 'load-balancer-api-internal: tcp connection to a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 7.661569ms message: 'load-balancer-api-internal: resolved host name a847322e14ca643f5a881460d71b35bf-2abf6ab4e0c92b67.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:20:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-network-check-target-ip-10-0-133-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "33434" uid: 04d7d67b-bf8e-4f4b-871d-7ed1d5395342 spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:46Z" message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.812µs message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 1.419117ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 873.838µs message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:19:46Z" - latency: 1.123456ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:18:46Z" - latency: 897.52µs message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:17:46Z" - latency: 1.54925ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:16:46Z" - latency: 1.107997ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:15:46Z" - latency: 1.286271ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:46Z" - latency: 1.304099ms message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:46Z" - latency: 899.736µs message: 'network-check-target-ip-10-0-133-60: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-network-check-target-ip-10-0-135-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "33433" uid: fb0f5ce7-6475-4fa5-ac04-6adf6d252884 spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:46Z" message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239086ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 2.487982ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 2.137436ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:19:46Z" - latency: 2.03379ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:18:46Z" - latency: 2.333944ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:17:46Z" - latency: 2.110047ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:16:46Z" - latency: 2.356201ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:15:46Z" - latency: 2.056734ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:46Z" - latency: 2.2948ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:46Z" - latency: 2.281514ms message: 'network-check-target-ip-10-0-135-245: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-network-check-target-ip-10-0-143-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "33432" uid: 5399261e-feee-4f02-83d1-6f1041359612 spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T20:07:46Z" message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.832481ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 2.36474ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 1.874336ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:19:46Z" - latency: 1.877263ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:18:46Z" - latency: 1.895932ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:17:46Z" - latency: 1.887167ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:16:46Z" - latency: 1.750015ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:15:46Z" - latency: 1.635992ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:14:46Z" - latency: 1.766464ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:13:46Z" - latency: 2.354457ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:12:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-60-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-60.ec2.internal uid: ad1eccea-ac80-4102-9676-f6ce10cba43d resourceVersion: "35746" uid: 3f80ec81-caf0-4d23-9136-102fb37afb8c spec: sourcePod: network-check-source-8894fc9bd-4wqkr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T20:06:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:24:46Z" - latency: 2.013995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:24:46Z" - latency: 998.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:23:46Z" - latency: 2.064861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:23:46Z" - latency: 847.747µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:22:46Z" - latency: 1.881698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:22:46Z" - latency: 1.185496ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:21:46Z" - latency: 1.871271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:21:46Z" - latency: 848.563µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:20:46Z" - latency: 1.970533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:20:46Z" kind: List metadata: resourceVersion: ""