apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "25921" uid: 22e91079-7499-43fa-b4eb-9a522db4a800 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T01:36:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 971.303µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 1.210247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 1.007553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:19Z" - latency: 1.128546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:19Z" - latency: 925.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:19Z" - latency: 1.054584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:19Z" - latency: 915.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:19Z" - latency: 1.041918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:19Z" - latency: 994.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "27054" uid: e363ae3c-5b39-4893-921d-4fe6698dca90 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:35:19Z" message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.13361ms message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:19Z" - latency: 7.707051ms message: 'load-balancer-api-external: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:59:19Z" - latency: 5.160659ms message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:19Z" - latency: 8.08075ms message: 'load-balancer-api-external: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:19Z" - latency: 5.261044ms message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 7.591462ms message: 'load-balancer-api-external: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:19Z" - latency: 4.577971ms message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 7.755303ms message: 'load-balancer-api-external: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:19Z" - latency: 4.328044ms message: 'load-balancer-api-external: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 7.10382ms message: 'load-balancer-api-external: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "27055" uid: ea0beab3-166b-41bd-bd79-d90f4cff1534 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:35:19Z" message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.109965ms message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:19Z" - latency: 7.624099ms message: 'load-balancer-api-internal: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:59:19Z" - latency: 5.116639ms message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:19Z" - latency: 8.131515ms message: 'load-balancer-api-internal: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:19Z" - latency: 5.194523ms message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 7.558271ms message: 'load-balancer-api-internal: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:19Z" - latency: 3.75398ms message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 7.844382ms message: 'load-balancer-api-internal: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:19Z" - latency: 5.027109ms message: 'load-balancer-api-internal: tcp connection to a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 7.170619ms message: 'load-balancer-api-internal: resolved host name a3bedeaf0e17146d7a4ea661009bd4da-62bfa081dd5c1337.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-128-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "25920" uid: 335a9488-9683-4260-a946-ceec1d1f4616 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:36:19Z" message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.87452ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 2.156638ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 2.063646ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 2.368251ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:19Z" - latency: 2.641939ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:19Z" - latency: 2.572126ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:19Z" - latency: 2.541684ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:19Z" - latency: 2.203652ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:19Z" - latency: 2.4559ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:19Z" - latency: 2.319813ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-135-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "25919" uid: 2f84b231-e076-4797-9dfe-0022c9e5d4ae spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:36:19Z" message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458628ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 2.335994ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 1.992863ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 2.462555ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:19Z" - latency: 2.57735ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:19Z" - latency: 2.288773ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:19Z" - latency: 2.339178ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:19Z" - latency: 2.289642ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:19Z" - latency: 2.39036ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:19Z" - latency: 2.240097ms message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-network-check-target-ip-10-0-143-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "25918" uid: 1a35e4c1-f250-4913-8ce6-bd32bc75aad6 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:36:19Z" message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.569839ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 1.478425ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 1.036564ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 1.238413ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:19Z" - latency: 953.139µs message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:19Z" - latency: 1.63653ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:19Z" - latency: 1.085386ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:19Z" - latency: 1.036714ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:19Z" - latency: 935.82µs message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:49:19Z" - latency: 1.202424ms message: 'network-check-target-ip-10-0-143-186: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:48:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:29:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-186.ec2.internal uid: 766a3f13-585f-4fa6-b186-099e4fabbbfe resourceVersion: "27052" uid: 287fbba0-aeb6-4650-a69b-fa5af87d5ee6 spec: sourcePod: network-check-source-7d88cb55d8-hrdd9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T01:35:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.106423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:19Z" - latency: 1.884589ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:59:19Z" - latency: 1.138346ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:19Z" - latency: 1.992595ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:19Z" - latency: 1.302809ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:19Z" - latency: 1.937655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:19Z" - latency: 1.136275ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:19Z" - latency: 1.765811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:19Z" - latency: 1.019812ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:19Z" - latency: 1.896729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:19Z" kind: List metadata: resourceVersion: ""