apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "38590" uid: 9fa57ceb-af06-43db-84ba-c67758e28363 spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T02:08:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.045943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 1.022134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 914.883µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:20:51Z" - latency: 1.131543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:19:51Z" - latency: 894.598µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:18:51Z" - latency: 872.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:17:51Z" - latency: 1.013987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:16:51Z" - latency: 1.393329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:15:51Z" - latency: 901.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:14:51Z" - latency: 845.777µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "42744" uid: 1ef4eb46-8516-475f-b503-faa8feb27991 spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T02:07:51Z" message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.017091ms message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:25:51Z" - latency: 7.796003ms message: 'load-balancer-api-external: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:25:51Z" - latency: 3.814406ms message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:24:51Z" - latency: 8.655671ms message: 'load-balancer-api-external: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:24:51Z" - latency: 4.109339ms message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:23:51Z" - latency: 7.619214ms message: 'load-balancer-api-external: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:23:51Z" - latency: 3.621405ms message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 9.023193ms message: 'load-balancer-api-external: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:22:51Z" - latency: 5.314576ms message: 'load-balancer-api-external: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 8.569782ms message: 'load-balancer-api-external: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "42747" uid: b12f257e-a3c0-437e-9970-f55a50b9774a spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T02:07:51Z" message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.78486ms message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:25:51Z" - latency: 7.746576ms message: 'load-balancer-api-internal: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:25:51Z" - latency: 5.019063ms message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:24:51Z" - latency: 8.687428ms message: 'load-balancer-api-internal: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:24:51Z" - latency: 4.226859ms message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:23:51Z" - latency: 7.566179ms message: 'load-balancer-api-internal: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:23:51Z" - latency: 5.013611ms message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 9.007073ms message: 'load-balancer-api-internal: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:22:51Z" - latency: 3.539901ms message: 'load-balancer-api-internal: tcp connection to a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 8.55077ms message: 'load-balancer-api-internal: resolved host name a676801c688af47b69a1924dd5c937ea-6d1be8c8ffebd657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T02:21:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-network-check-target-ip-10-0-129-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "38588" uid: 4c0d9b40-cf55-4ab0-b726-ca1135041323 spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T02:08:51Z" message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.240963ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 2.201299ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 2.113013ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:20:51Z" - latency: 1.990732ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:19:51Z" - latency: 2.478855ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:18:51Z" - latency: 2.171778ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:17:51Z" - latency: 2.626849ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:16:51Z" - latency: 2.188996ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:15:51Z" - latency: 2.183294ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:14:51Z" - latency: 1.876708ms message: 'network-check-target-ip-10-0-129-184: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-network-check-target-ip-10-0-135-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "38587" uid: b8ec6526-92a2-4c87-8eff-59c3d251698a spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T02:08:51Z" message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.363µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 819.697µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 1.207071ms message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:20:51Z" - latency: 955.009µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:19:51Z" - latency: 822.163µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:18:51Z" - latency: 1.240271ms message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:17:51Z" - latency: 896.559µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:16:51Z" - latency: 812.308µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:15:51Z" - latency: 907.08µs message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:14:51Z" - latency: 1.09607ms message: 'network-check-target-ip-10-0-135-168: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-network-check-target-ip-10-0-141-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "38589" uid: de52ff28-cf0f-414b-8506-228efbbb0a88 spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T02:08:51Z" message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.471916ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 2.284564ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 2.290817ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:20:51Z" - latency: 1.895085ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:19:51Z" - latency: 2.274158ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:18:51Z" - latency: 2.34699ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:17:51Z" - latency: 2.369832ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:16:51Z" - latency: 2.266473ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:15:51Z" - latency: 2.387185ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:14:51Z" - latency: 2.12102ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:13:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T02:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-168-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-168.ec2.internal uid: 30953575-8f71-4cbe-af8e-72ee35acb808 resourceVersion: "42745" uid: 7efb3a40-aa49-494f-922f-4dc7cc70fcc6 spec: sourcePod: network-check-source-7bc5b6bf85-zjxlq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T02:07:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.064443ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:25:51Z" - latency: 1.828055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T02:25:51Z" - latency: 974.531µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:24:51Z" - latency: 2.375269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T02:24:51Z" - latency: 961.69µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:23:51Z" - latency: 1.891412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T02:23:51Z" - latency: 924.894µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:22:51Z" - latency: 1.69484ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T02:22:51Z" - latency: 928.407µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T02:21:51Z" - latency: 1.609627ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T02:21:51Z" kind: List metadata: resourceVersion: ""