apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32266" uid: ca260dac-e6b1-45d7-9d1a-381da87c29f7 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T17:50:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.097092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 1.463981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 1.130732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 1.023819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 1.171693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 1.032607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:23Z" - latency: 1.432838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:23Z" - latency: 955.757µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:23Z" - latency: 877.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:17:23Z" - latency: 868.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32268" uid: b96e4356-2379-49cd-ab11-393f36f081d3 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:49:23Z" message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.742912ms message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 8.812516ms message: 'load-balancer-api-external: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:23Z" - latency: 6.81813ms message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 11.938785ms message: 'load-balancer-api-external: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:23Z" - latency: 5.618369ms message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 8.643856ms message: 'load-balancer-api-external: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:23Z" - latency: 5.408894ms message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 8.745774ms message: 'load-balancer-api-external: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:23Z" - latency: 7.280417ms message: 'load-balancer-api-external: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 9.206545ms message: 'load-balancer-api-external: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32267" uid: 07ed208d-cb68-4c09-b6da-5fdaecf20ac9 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:49:23Z" message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.682714ms message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 8.842198ms message: 'load-balancer-api-internal: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:23Z" - latency: 6.885383ms message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 12.026251ms message: 'load-balancer-api-internal: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:23Z" - latency: 5.612127ms message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 8.678849ms message: 'load-balancer-api-internal: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:23Z" - latency: 5.805665ms message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 8.85986ms message: 'load-balancer-api-internal: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:23Z" - latency: 5.003544ms message: 'load-balancer-api-internal: tcp connection to a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 9.234248ms message: 'load-balancer-api-internal: resolved host name a4194a9e6809b457ebc2cbb5f9b82208-0249c43e72e4d47d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-network-check-target-ip-10-0-133-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32264" uid: 2234b428-8cb4-457f-bd7b-477c4b771f48 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:23Z" message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.090567ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 1.930782ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 1.971615ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 2.199797ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 2.651274ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 1.847856ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:23Z" - latency: 1.945659ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:23Z" - latency: 2.162004ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:23Z" - latency: 1.844932ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:17:23Z" - latency: 1.969962ms message: 'network-check-target-ip-10-0-133-63: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-network-check-target-ip-10-0-136-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32262" uid: 3743eb3a-fd66-4b55-8048-a84cbd9a65b1 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:23Z" message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.34782ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 2.333252ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 2.209653ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 2.124008ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 2.823314ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 2.459325ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:23Z" - latency: 2.349563ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:23Z" - latency: 2.251136ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:23Z" - latency: 2.251332ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:17:23Z" - latency: 2.066474ms message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-network-check-target-ip-10-0-141-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32263" uid: cf553563-2350-4849-84e9-81f2fd1bb0e4 spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:50:23Z" message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229652ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 937.757µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 998.508µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 979.534µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 849.327µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 776.596µs message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:20:23Z" - latency: 1.45822ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:19:23Z" - latency: 1.171645ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:18:23Z" - latency: 1.370092ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:17:23Z" - latency: 1.209912ms message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:16:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T17:43:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-169.ec2.internal uid: a6e764d5-4075-4ae8-97eb-d29c5e9f563b resourceVersion: "32265" uid: d76b7ab1-f263-4cf0-bac3-4c930e87c20d spec: sourcePod: network-check-source-869dcfcdcd-pbjck targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T17:49:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.807µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:25:23Z" - latency: 2.093489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:25:23Z" - latency: 1.095649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:24:23Z" - latency: 2.065221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:24:23Z" - latency: 939.809µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:23:23Z" - latency: 1.838359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:23:23Z" - latency: 850.007µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:22:23Z" - latency: 1.674151ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:22:23Z" - latency: 841.72µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:21:23Z" - latency: 3.09144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:21:23Z" kind: List metadata: resourceVersion: ""