apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "22256" uid: cfb5a7b8-5721-4f95-a2f7-f708e8c4bf16 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T10:09:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:23:02Z" - latency: 1.264346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:22:02Z" - latency: 820.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:21:02Z" - latency: 1.360844ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 1.373061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 931.158µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 1.314939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 997.645µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 1.140796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:15:02Z" - latency: 1.177855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "20636" uid: 267c39a6-f790-4c9c-8075-e3dedec65b79 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:02Z" message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.018018ms message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 7.19226ms message: 'load-balancer-api-external: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:20:02Z" - latency: 5.325671ms message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 8.275157ms message: 'load-balancer-api-external: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:19:02Z" - latency: 4.992246ms message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 7.179087ms message: 'load-balancer-api-external: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:18:02Z" - latency: 4.784998ms message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 6.718411ms message: 'load-balancer-api-external: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:17:02Z" - latency: 5.362549ms message: 'load-balancer-api-external: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 7.272179ms message: 'load-balancer-api-external: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:16:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "20635" uid: 0089f29c-d283-4eb7-8230-7b807c870fb8 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:02Z" message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.918561ms message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 7.23554ms message: 'load-balancer-api-internal: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:20:02Z" - latency: 5.314925ms message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 8.297565ms message: 'load-balancer-api-internal: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:19:02Z" - latency: 5.259253ms message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 7.161089ms message: 'load-balancer-api-internal: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:18:02Z" - latency: 4.776874ms message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 6.689412ms message: 'load-balancer-api-internal: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:17:02Z" - latency: 5.392104ms message: 'load-balancer-api-internal: tcp connection to a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 7.341503ms message: 'load-balancer-api-internal: resolved host name a28580b1d39df4317baae046d3533e69-8ff350f4d834eafb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T10:16:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-128-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "22253" uid: 7010eae3-f6ad-4d9c-a49d-4164ae30a083 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:02Z" message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.374µs message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:23:02Z" - latency: 1.365849ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:22:02Z" - latency: 816.224µs message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:21:02Z" - latency: 1.293322ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 915.328µs message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 1.162597ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 1.174286ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 935.9µs message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 1.601226ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:15:02Z" - latency: 876.376µs message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-129-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "22255" uid: eed2adc5-da2a-4d39-8375-d8b8acccc188 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:02Z" message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267042ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:23:02Z" - latency: 2.099567ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:22:02Z" - latency: 2.16493ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:21:02Z" - latency: 2.274145ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 2.129013ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 2.665307ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 2.309157ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 2.474853ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 2.474165ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:15:02Z" - latency: 2.322973ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-network-check-target-ip-10-0-142-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "22254" uid: 7f911bf4-fff8-4928-9d2b-2b2a4ed42490 spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:09:02Z" message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.101692ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:23:02Z" - latency: 2.174785ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:22:02Z" - latency: 2.161347ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:21:02Z" - latency: 1.913333ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 2.148654ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 2.126624ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 2.231319ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 2.360271ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 2.095185ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:15:02Z" - latency: 2.212598ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:14:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:02:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-168-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-168.ec2.internal uid: 9e2298c9-4528-44b6-b391-dbb9b9f84501 resourceVersion: "20634" uid: 5bf0334f-7720-4909-9863-0d56a4158b3e spec: sourcePod: network-check-source-7bc5b6bf85-2lkwf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T10:08:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 808.139µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:20:02Z" - latency: 2.085721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:20:02Z" - latency: 843.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:19:02Z" - latency: 1.690996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:19:02Z" - latency: 1.047409ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:18:02Z" - latency: 1.803835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:18:02Z" - latency: 835.548µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:17:02Z" - latency: 1.525088ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:17:02Z" - latency: 832.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T10:16:02Z" - latency: 1.690918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T10:16:02Z" kind: List metadata: resourceVersion: ""