apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "24587" uid: 5a7b9f4c-dc54-410e-b791-6e76ebded2b3 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T17:17:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.065036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:17:54Z" - latency: 1.301406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:16:54Z" - latency: 967.767µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:15:54Z" - latency: 1.369741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:14:54Z" - latency: 1.108261ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:13:54Z" - latency: 1.252382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:12:54Z" - latency: 1.757662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:11:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "28670" uid: 9ecbaea8-84a1-42e6-b56c-61b6a3e26b7e spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T17:16:54Z" message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.816654ms message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:22:54Z" - latency: 6.592643ms message: 'load-balancer-api-external: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:22:54Z" - latency: 5.390969ms message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:21:54Z" - latency: 7.324208ms message: 'load-balancer-api-external: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:21:54Z" - latency: 3.563608ms message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:20:54Z" - latency: 6.652996ms message: 'load-balancer-api-external: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:20:54Z" - latency: 5.084945ms message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:19:54Z" - latency: 6.939695ms message: 'load-balancer-api-external: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:19:54Z" - latency: 4.374402ms message: 'load-balancer-api-external: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:18:54Z" - latency: 6.42123ms message: 'load-balancer-api-external: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:18:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "28669" uid: 3ceeefeb-69d4-41b3-bc97-3983a2e20af1 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T17:16:54Z" message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.83047ms message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:22:54Z" - latency: 6.556096ms message: 'load-balancer-api-internal: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:22:54Z" - latency: 5.412296ms message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:21:54Z" - latency: 7.261157ms message: 'load-balancer-api-internal: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:21:54Z" - latency: 4.256166ms message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:20:54Z" - latency: 6.615756ms message: 'load-balancer-api-internal: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:20:54Z" - latency: 5.093471ms message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:19:54Z" - latency: 6.949987ms message: 'load-balancer-api-internal: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:19:54Z" - latency: 4.335742ms message: 'load-balancer-api-internal: tcp connection to a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:18:54Z" - latency: 6.446744ms message: 'load-balancer-api-internal: resolved host name a28a3e945cda1429f827c98f06de68f1-9ca11ad7c1e64e11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T17:18:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-network-check-target-ip-10-0-129-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "24585" uid: 13438d3b-b881-4073-808a-7159cba7f453 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:17:54Z" message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.209312ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:17:54Z" - latency: 2.241551ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:16:54Z" - latency: 2.461872ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:15:54Z" - latency: 2.323258ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:14:54Z" - latency: 1.926072ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:13:54Z" - latency: 2.295709ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:12:54Z" - latency: 2.798659ms message: 'network-check-target-ip-10-0-129-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:11:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-network-check-target-ip-10-0-141-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "24586" uid: 43b5c1c8-d47b-4244-9a75-8a8f35ad5f31 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:17:54Z" message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.796279ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:17:54Z" - latency: 2.530997ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:16:54Z" - latency: 1.896951ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:15:54Z" - latency: 1.962314ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:14:54Z" - latency: 2.111916ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:13:54Z" - latency: 1.788212ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:12:54Z" - latency: 2.070569ms message: 'network-check-target-ip-10-0-141-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:11:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-network-check-target-ip-10-0-141-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "24584" uid: 93bfef1f-a350-4519-9438-e36b2ba0b447 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T17:17:54Z" message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.926µs message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:17:54Z" - latency: 1.627734ms message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:16:54Z" - latency: 964.788µs message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:15:54Z" - latency: 1.569705ms message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:14:54Z" - latency: 940.157µs message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:13:54Z" - latency: 1.002672ms message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:12:54Z" - latency: 1.993644ms message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:11:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T17:10:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-95.ec2.internal uid: 4e2c1d4c-cfb8-47e9-a4dc-b9c11a6dd853 resourceVersion: "28668" uid: a296e8d5-1cb7-4894-8ec9-16b0d113b927 spec: sourcePod: network-check-source-dbd9cf844-6mgzv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T17:16:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.228303ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:22:54Z" - latency: 1.802028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T17:22:54Z" - latency: 846.417µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:21:54Z" - latency: 1.69826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T17:21:54Z" - latency: 1.218499ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:20:54Z" - latency: 2.221116ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T17:20:54Z" - latency: 975.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:19:54Z" - latency: 2.214055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T17:19:54Z" - latency: 843.118µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T17:18:54Z" - latency: 2.108118ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T17:18:54Z" kind: List metadata: resourceVersion: ""