apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "69900" uid: 7c75b339-c9f7-436b-8071-1e8ed46c6f08 spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T21:00:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.177153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 1.499039ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 1.330241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 944.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:00:38Z" - latency: 1.132847ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:59:38Z" - latency: 935.158µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:58:38Z" - latency: 878.116µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:57:38Z" - latency: 762.396µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:56:38Z" - latency: 879.195µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:55:38Z" - latency: 841.296µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "71551" uid: a77788a9-a714-462d-82ed-883e36100f1e spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:59:38Z" message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.98129ms message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:05:38Z" - latency: 8.69766ms message: 'load-balancer-api-external: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:05:38Z" - latency: 5.40726ms message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:04:38Z" - latency: 8.123868ms message: 'load-balancer-api-external: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:04:38Z" - latency: 4.706497ms message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 9.235271ms message: 'load-balancer-api-external: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:03:38Z" - latency: 4.992836ms message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 8.336057ms message: 'load-balancer-api-external: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:02:38Z" - latency: 5.72788ms message: 'load-balancer-api-external: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 8.534362ms message: 'load-balancer-api-external: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:01:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "71550" uid: 9d74d779-ca43-4e1e-b097-955242099c10 spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:59:38Z" message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.484029ms message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:05:38Z" - latency: 8.775952ms message: 'load-balancer-api-internal: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:05:38Z" - latency: 5.257078ms message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:04:38Z" - latency: 8.010462ms message: 'load-balancer-api-internal: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:04:38Z" - latency: 3.981918ms message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 9.321875ms message: 'load-balancer-api-internal: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:03:38Z" - latency: 6.977696ms message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 8.189139ms message: 'load-balancer-api-internal: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:02:38Z" - latency: 3.828157ms message: 'load-balancer-api-internal: tcp connection to abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 8.429348ms message: 'load-balancer-api-internal: resolved host name abaf5193e534b40249842268ba26c882-888467585308f7a3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:01:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-131-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "69897" uid: e6db3f09-0c15-485e-a89e-b55967ef1b2f spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:00:38Z" message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.71µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 847.688µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 800.543µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 1.161426ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:00:38Z" - latency: 1.319264ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:59:38Z" - latency: 1.390435ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:58:38Z" - latency: 808.36µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:57:38Z" - latency: 1.271703ms message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:56:38Z" - latency: 820.153µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:55:38Z" - latency: 783.845µs message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-134-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "69898" uid: c546d4e7-6bf9-4100-a553-54cb81424539 spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:00:38Z" message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.858395ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 1.724019ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 1.615823ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 1.824039ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:00:38Z" - latency: 2.019162ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:59:38Z" - latency: 1.529676ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:58:38Z" - latency: 1.587804ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:57:38Z" - latency: 1.924157ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:56:38Z" - latency: 1.802577ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:55:38Z" - latency: 1.726466ms message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-140-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "69899" uid: 3c91496a-f4c1-456e-931f-1fedef26f529 spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T21:00:38Z" message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.280336ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 2.196737ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 2.077796ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 2.296642ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:00:38Z" - latency: 2.135303ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:59:38Z" - latency: 2.194364ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:58:38Z" - latency: 2.251599ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:57:38Z" - latency: 2.352431ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:56:38Z" - latency: 2.443454ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:55:38Z" - latency: 2.145897ms message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T21:54:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:53:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-165-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-165.ec2.internal uid: c10268b9-8926-408b-bbfc-b3e8e0284530 resourceVersion: "71549" uid: d41004cd-4dd9-4dba-a53b-3c7cea9e845a spec: sourcePod: network-check-source-989f8b8dc-j67bg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:59:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.094µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:05:38Z" - latency: 1.817106ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:05:38Z" - latency: 961.597µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:04:38Z" - latency: 2.220676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:04:38Z" - latency: 925.182µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:03:38Z" - latency: 2.046664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:03:38Z" - latency: 817.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:02:38Z" - latency: 1.776657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:02:38Z" - latency: 769.346µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:01:38Z" - latency: 1.626845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:01:38Z" kind: List metadata: resourceVersion: ""