apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "49338" uid: 2749998e-5480-43ad-813e-f47363c8b58d spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T14:17:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.395µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:24Z" - latency: 1.07199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:24Z" - latency: 1.35404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:24Z" - latency: 761.866µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:24Z" - latency: 955.156µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:24Z" - latency: 753.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 1.090792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 952.297µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 961.057µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 1.074005ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "44237" uid: 624d0944-d9e0-4e13-a93c-0ca9aedb6534 spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:16:24Z" message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.477782ms message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 6.052542ms message: 'load-balancer-api-external: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:40:24Z" - latency: 4.17038ms message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 6.883868ms message: 'load-balancer-api-external: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:39:24Z" - latency: 4.973679ms message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 6.982756ms message: 'load-balancer-api-external: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:38:24Z" - latency: 4.59372ms message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 7.601408ms message: 'load-balancer-api-external: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:37:24Z" - latency: 6.038791ms message: 'load-balancer-api-external: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - latency: 6.618496ms message: 'load-balancer-api-external: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "44236" uid: 628bc8fb-7095-4ce4-9eb8-082ef41e8061 spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:16:24Z" message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.749293ms message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 6.020096ms message: 'load-balancer-api-internal: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:40:24Z" - latency: 4.138966ms message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 6.969401ms message: 'load-balancer-api-internal: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:39:24Z" - latency: 4.304515ms message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 6.928994ms message: 'load-balancer-api-internal: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:38:24Z" - latency: 3.459261ms message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 7.563591ms message: 'load-balancer-api-internal: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:37:24Z" - latency: 4.449565ms message: 'load-balancer-api-internal: tcp connection to ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - latency: 6.68274ms message: 'load-balancer-api-internal: resolved host name ac4b8a6588482439bb37150c5b454437-41a65e9b433eaaf3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-136-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "49336" uid: 8ea60416-a790-480a-b9f0-148fff341bb2 spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:17:24Z" message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.997039ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:24Z" - latency: 2.198198ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:24Z" - latency: 2.281907ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:24Z" - latency: 2.061939ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:24Z" - latency: 1.748386ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:24Z" - latency: 1.856831ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 2.072599ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 1.973935ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 2.085928ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 1.908751ms message: 'network-check-target-ip-10-0-136-116: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-137-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "49335" uid: 3aa833e5-abc2-4cc8-98c7-4108d7535c71 spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:17:24Z" message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.336µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:24Z" - latency: 1.424481ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:24Z" - latency: 1.347985ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:24Z" - latency: 1.068954ms message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:24Z" - latency: 741.83µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:24Z" - latency: 791.544µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 840.879µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 986.445µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 915.24µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 850.616µs message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-142-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "49337" uid: 98e55a12-97e6-495b-a020-f097cd6aa8c5 spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:17:24Z" message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.964759ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:24Z" - latency: 1.815905ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:24Z" - latency: 1.716161ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:24Z" - latency: 1.822193ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:24Z" - latency: 2.110794ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:24Z" - latency: 1.922754ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 2.036661ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 1.945502ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 1.888415ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 1.975036ms message: 'network-check-target-ip-10-0-142-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-228.ec2.internal uid: 7704ba96-a175-4f3f-8f61-39be39678421 resourceVersion: "44234" uid: 98c65b01-958d-4b05-9f34-2a9cb9dc73dd spec: sourcePod: network-check-source-7f44b6dd87-9mv7r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T14:16:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.878µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:24Z" - latency: 1.528604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:40:24Z" - latency: 872.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:24Z" - latency: 1.783998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:39:24Z" - latency: 989.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:38:24Z" - latency: 1.905701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:38:24Z" - latency: 950.591µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:37:24Z" - latency: 1.779814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:37:24Z" - latency: 965.056µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:24Z" - latency: 2.05093ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:24Z" kind: List metadata: resourceVersion: ""