apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62091" uid: b9d69842-02bf-4673-8ef0-eb15a689764f spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T16:55: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.313474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 1.182501ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 1.180755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 837.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 1.111686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 1.557327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:25:23Z" - latency: 998.674µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:24:23Z" - latency: 862.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:23:23Z" - latency: 1.209104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:22:23Z" - latency: 851.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62093" uid: fed7945e-55fc-496f-a8bc-7cfe3bc80001 spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:54:23Z" message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.233437ms message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 6.854181ms message: 'load-balancer-api-external: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:30:23Z" - latency: 4.810205ms message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 11.331176ms message: 'load-balancer-api-external: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:29:23Z" - latency: 4.481937ms message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 6.615561ms message: 'load-balancer-api-external: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:28:23Z" - latency: 6.679753ms message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 7.746827ms message: 'load-balancer-api-external: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:27:23Z" - latency: 5.422987ms message: 'load-balancer-api-external: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 7.012724ms message: 'load-balancer-api-external: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62092" uid: 05cbf54b-18c5-4f5c-8825-25d8a1c78c1a spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:54:23Z" message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.224666ms message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 6.738026ms message: 'load-balancer-api-internal: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:30:23Z" - latency: 5.005817ms message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 11.398396ms message: 'load-balancer-api-internal: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:29:23Z" - latency: 4.514785ms message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 6.660975ms message: 'load-balancer-api-internal: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:28:23Z" - latency: 6.714271ms message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 7.779843ms message: 'load-balancer-api-internal: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:27:23Z" - latency: 5.434374ms message: 'load-balancer-api-internal: tcp connection to a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 6.90881ms message: 'load-balancer-api-internal: resolved host name a5eb8e9b9462841b1a12ce83056f3175-92f141094ebc3b92.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T17:26:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-network-check-target-ip-10-0-128-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62089" uid: 525dfffe-db4f-443f-8569-86aa8c2b4286 spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:55:23Z" message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.542716ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 2.428539ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 2.305427ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 2.137444ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 2.724021ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 3.286033ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:25:23Z" - latency: 2.139792ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:24:23Z" - latency: 2.311708ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:23:23Z" - latency: 2.350378ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:22:23Z" - latency: 2.309499ms message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-network-check-target-ip-10-0-130-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62088" uid: 2818f37e-ddde-4dbb-81dc-85e5ae6117d5 spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:55:23Z" message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365311ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 2.247482ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 2.488276ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 2.233157ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 2.335952ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 2.714881ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:25:23Z" - latency: 2.201899ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:24:23Z" - latency: 2.45608ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:23:23Z" - latency: 2.401651ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:22:23Z" - latency: 2.113962ms message: 'network-check-target-ip-10-0-130-18: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-network-check-target-ip-10-0-131-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62087" uid: acf737d7-0d9e-432b-8040-ee98ed4b76d5 spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:55:23Z" message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040474ms message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 881.094µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 982.861µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 1.002791ms message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 990.721µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 2.022329ms message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:25:23Z" - latency: 991.862µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:24:23Z" - latency: 833.877µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:23:23Z" - latency: 1.449276ms message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:22:23Z" - latency: 914.498µs message: 'network-check-target-ip-10-0-131-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:21:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:48:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-206.ec2.internal uid: e85d197b-643c-474a-911b-0d62e7cedfaa resourceVersion: "62090" uid: 16f36f79-298e-4e57-89cf-8730f8879b02 spec: sourcePod: network-check-source-7bc5b6bf85-rcfkm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T16:54:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.235µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:30:23Z" - latency: 1.988658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:30:23Z" - latency: 770.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:29:23Z" - latency: 2.032259ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:29:23Z" - latency: 842.016µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:28:23Z" - latency: 1.818971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:28:23Z" - latency: 1.079849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:27:23Z" - latency: 1.89453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:27:23Z" - latency: 912.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T17:26:23Z" - latency: 1.885241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T17:26:23Z" kind: List metadata: resourceVersion: ""