apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "38507" uid: 36911919-e04a-49e9-9ccb-be5b483b4907 spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:40:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:46:59Z" - latency: 992.779µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:45:59Z" - latency: 2.084963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 1.054383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 1.037733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 1.533794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 1.260825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 1.051788ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:59Z" - latency: 1.209465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:59Z" - latency: 852.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "33139" uid: e3638848-d8e0-4285-8d39-3346c53f2a89 spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:39:00Z" message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.951605ms message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 7.275782ms message: 'load-balancer-api-external: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:44:59Z" - latency: 17.097055ms message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 6.929193ms message: 'load-balancer-api-external: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:43:59Z" - latency: 15.801226ms message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 7.203952ms message: 'load-balancer-api-external: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:42:59Z" - latency: 15.611918ms message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 8.51468ms message: 'load-balancer-api-external: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:59Z" - latency: 18.301151ms message: 'load-balancer-api-external: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 7.231533ms message: 'load-balancer-api-external: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "33138" uid: b6887ea7-75a2-4aeb-9555-deb00f4599b1 spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:39:00Z" message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.231403ms message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 7.237315ms message: 'load-balancer-api-internal: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:44:59Z" - latency: 17.136645ms message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 6.878753ms message: 'load-balancer-api-internal: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:43:59Z" - latency: 15.768569ms message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 7.148679ms message: 'load-balancer-api-internal: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:42:59Z" - latency: 13.674171ms message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 8.419846ms message: 'load-balancer-api-internal: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:59Z" - latency: 17.407031ms message: 'load-balancer-api-internal: tcp connection to ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 7.075903ms message: 'load-balancer-api-internal: resolved host name ad1c9def951c3486c987d25017e9e9cc-3acd125417877706.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-130-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "38504" uid: 942e7c10-8b39-4e87-bc74-ac83094a112d spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:39:59Z" message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 995.277µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:46:59Z" - latency: 920.335µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:45:59Z" - latency: 1.552952ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 1.310645ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 919.032µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 2.818497ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 1.433686ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 853.11µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:59Z" - latency: 936.395µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:59Z" - latency: 891.097µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-136-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "38506" uid: 9add87e9-06d2-45e4-9105-84dbb4464f12 spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:39:59Z" message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.764036ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:46:59Z" - latency: 2.372575ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:45:59Z" - latency: 2.679127ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 2.131402ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 2.433247ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 4.388024ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 2.624438ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 2.260565ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:59Z" - latency: 2.230146ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:59Z" - latency: 2.083909ms message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-136-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "38505" uid: 6dbe5313-7994-4dca-9701-26793b26701c spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:39:59Z" message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.460995ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:46:59Z" - latency: 2.541353ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:45:59Z" - latency: 2.563079ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 2.744596ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 2.410893ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 4.108585ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 2.582799ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 2.179329ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:59Z" - latency: 2.908047ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:59Z" - latency: 3.009085ms message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:32:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 9e2f923e-7c1c-45cd-9676-508e943d6b78 resourceVersion: "33136" uid: 678fb1c5-a176-420d-9a08-02826956e28e spec: sourcePod: network-check-source-6f78d59f99-xjnjf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:38:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.138772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:44:59Z" - latency: 2.013721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:44:59Z" - latency: 1.204857ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:43:59Z" - latency: 1.850308ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:43:59Z" - latency: 929.511µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:59Z" - latency: 2.264048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:42:59Z" - latency: 2.52509ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:59Z" - latency: 3.276092ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:59Z" - latency: 1.163413ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:59Z" - latency: 2.199837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:59Z" kind: List metadata: resourceVersion: ""