apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "165503" uid: dd69e148-963a-4ced-bec7-4ead5b11b699 spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T21:17:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.301983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:58Z" - latency: 1.036679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:58Z" - latency: 984.744µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:58Z" - latency: 6.766272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:58Z" - latency: 7.577162ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 967.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 969.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 1.916566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 977.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 1.003187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "162521" uid: 9c7f8ea8-1675-4bf3-a500-624925d138b4 spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:16:59Z" message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 58.159825ms message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 45.753791ms message: 'load-balancer-api-external: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:58:58Z" - latency: 51.978933ms message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 6.386751ms message: 'load-balancer-api-external: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:57:58Z" - latency: 51.065016ms message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 6.914835ms message: 'load-balancer-api-external: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:56:58Z" - latency: 51.635816ms message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 8.573085ms message: 'load-balancer-api-external: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:55:58Z" - latency: 54.377366ms message: 'load-balancer-api-external: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 7.330703ms message: 'load-balancer-api-external: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:54:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "162522" uid: b8799db1-7679-419f-a514-89668c48bbea spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T21:16:59Z" message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 58.576606ms message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 46.313333ms message: 'load-balancer-api-internal: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:58:58Z" - latency: 55.458022ms message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 6.359685ms message: 'load-balancer-api-internal: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:57:58Z" - latency: 55.225586ms message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 6.864972ms message: 'load-balancer-api-internal: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:56:58Z" - latency: 51.356715ms message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 8.49024ms message: 'load-balancer-api-internal: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:55:58Z" - latency: 51.001027ms message: 'load-balancer-api-internal: tcp connection to ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 7.259244ms message: 'load-balancer-api-internal: resolved host name ab303f828c2034a3dad08796677c6e91-0df893518692fff8.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T22:54:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-network-check-target-ip-10-0-128-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "165499" uid: f2f62908-5c39-4db2-b803-c45d2fae3370 spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:17:58Z" message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.562466ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:58Z" - latency: 1.168734ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:58Z" - latency: 1.445024ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:58Z" - latency: 2.093895ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:58Z" - latency: 7.802375ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 1.128352ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 1.007067ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 1.00344ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 1.115967ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 1.333709ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-network-check-target-ip-10-0-133-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "165501" uid: 58271357-d1c7-43f2-bf56-60165689e3d3 spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:17:58Z" message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.865082ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:58Z" - latency: 2.490537ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:58Z" - latency: 2.022281ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:58Z" - latency: 7.99631ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:58Z" - latency: 6.474536ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 2.640901ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 2.492644ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 2.627991ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 2.605559ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 2.031895ms message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-network-check-target-ip-10-0-137-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "165500" uid: 0e13666f-ec4b-4fa5-8196-cb6bce6a7f7a spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T21:17:58Z" message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.356509ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:58Z" - latency: 2.337182ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:58Z" - latency: 2.534535ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:58Z" - latency: 9.499949ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:58Z" - latency: 6.690899ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:58Z" - latency: 2.277518ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:58Z" - latency: 2.278917ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:58Z" - latency: 2.280433ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:58Z" - latency: 2.689372ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:58Z" - latency: 2.290316ms message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:53:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:10:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-89-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-89.us-west-2.compute.internal uid: 5056c7b5-e5f2-48a1-966a-447ed2eea650 resourceVersion: "162520" uid: dfe32a2b-2028-440d-b46e-b50b58cef865 spec: sourcePod: network-check-source-6f78d59f99-8jclh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T21:16:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.953874ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:59Z" - latency: 9.275954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:58:59Z" - latency: 1.120002ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:59Z" - latency: 759.841µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:57:59Z" - latency: 1.139468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:59Z" - latency: 709.601µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:56:59Z" - latency: 898.904µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:59Z" - latency: 702.462µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:55:59Z" - latency: 1.361549ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:54:59Z" - latency: 543.982µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T22:54:59Z" kind: List metadata: resourceVersion: ""