apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "30990" uid: edc7a936-15ca-4e11-9452-1bd31636fc27 spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T05:42:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 933.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:38Z" - latency: 1.000102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:38Z" - latency: 1.106024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 1.039277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 930.802µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 1.011163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 801.734µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 1.125944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:38Z" - latency: 1.228351ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:38Z" - latency: 1.001526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "27817" uid: 4ee07c65-d8fd-44f2-8c25-625a729d2dcd spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T05:41:38Z" message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.581874ms message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 7.920868ms message: 'load-balancer-api-external: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:47:38Z" - latency: 18.099338ms message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 6.739468ms message: 'load-balancer-api-external: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:46:38Z" - latency: 17.318036ms message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 7.660726ms message: 'load-balancer-api-external: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:45:38Z" - latency: 17.074092ms message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 7.397449ms message: 'load-balancer-api-external: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:44:38Z" - latency: 21.554399ms message: 'load-balancer-api-external: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 6.836495ms message: 'load-balancer-api-external: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:43:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "27818" uid: cc7afb34-22e7-4569-be77-11c9a754d9dc spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T05:41:38Z" message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.838846ms message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 7.881331ms message: 'load-balancer-api-internal: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:47:38Z" - latency: 17.616992ms message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 6.694049ms message: 'load-balancer-api-internal: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:46:38Z" - latency: 16.857726ms message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 7.627054ms message: 'load-balancer-api-internal: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:45:38Z" - latency: 17.135035ms message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 7.372825ms message: 'load-balancer-api-internal: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:44:38Z" - latency: 15.973114ms message: 'load-balancer-api-internal: tcp connection to a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 6.783522ms message: 'load-balancer-api-internal: resolved host name a285f8f410ab746dcbbaf79493336aa9-20710d9bc72a8694.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:43:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-131-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "30988" uid: 29adf2ff-f76f-48ae-99a3-08e1f67ea5a4 spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T05:42:38Z" message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.835159ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:38Z" - latency: 2.377522ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:38Z" - latency: 2.108393ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 1.8987ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 2.318902ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 1.887293ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 2.063489ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 1.859179ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:38Z" - latency: 1.994949ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:38Z" - latency: 1.69465ms message: 'network-check-target-ip-10-0-131-217: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-136-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "30985" uid: a073459e-c484-41c1-83c2-463ba9aa5f7d spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T05:42:38Z" message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:38Z" - latency: 1.424623ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:38Z" - latency: 838.971µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 875.794µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 1.256888ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 973.914µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 1.239734ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 838.472µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:38Z" - latency: 865.856µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:38Z" - latency: 1.026319ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-141-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "30986" uid: ca1b0339-eae7-4afa-8677-82ce2a50ddf8 spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T05:42:38Z" message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.200385ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:38Z" - latency: 2.147528ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:38Z" - latency: 2.183373ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 2.244293ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 2.303861ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 2.392581ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 2.219064ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 2.027631ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:38Z" - latency: 2.182435ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:38Z" - latency: 2.722774ms message: 'network-check-target-ip-10-0-141-106: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T05:35:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: 2f46b0f4-0486-4fa1-980f-8d9fcea01b25 resourceVersion: "27816" uid: 1e5aba8e-d14b-4bed-9a7d-3aea6005d273 spec: sourcePod: network-check-source-6f78d59f99-vsmsp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T05:41:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.042309ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:38Z" - latency: 1.870427ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:47:38Z" - latency: 1.019217ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:38Z" - latency: 1.85004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:46:38Z" - latency: 1.452937ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:38Z" - latency: 1.671462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:45:38Z" - latency: 1.290533ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:38Z" - latency: 1.875125ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:44:38Z" - latency: 861.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:38Z" - latency: 2.04283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:43:38Z" kind: List metadata: resourceVersion: ""