apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "40218" uid: da55491e-19f6-4fa6-8958-c863a7f595e5 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:28:14Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:17:14Z" - latency: 1.225692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:16:14Z" - latency: 831.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 1.501564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 807.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 992.558µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 930.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 1.064034ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:14Z" - latency: 1.232412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:14Z" - latency: 1.182372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "39083" uid: a326fbc8-bf65-421b-9156-cef3cc5ab327 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:27:14Z" message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.880049ms message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 7.934709ms message: 'load-balancer-api-external: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:15:14Z" - latency: 4.525971ms message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 7.486612ms message: 'load-balancer-api-external: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:14Z" - latency: 4.374864ms message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 8.256145ms message: 'load-balancer-api-external: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:14Z" - latency: 4.66254ms message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 7.669916ms message: 'load-balancer-api-external: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:14Z" - latency: 5.055045ms message: 'load-balancer-api-external: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 8.733143ms message: 'load-balancer-api-external: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "39082" uid: ed4d4d9b-ec36-4fc4-b009-b3754cd84c44 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:27:14Z" message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.798405ms message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 7.978478ms message: 'load-balancer-api-internal: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:15:14Z" - latency: 4.504185ms message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 7.511449ms message: 'load-balancer-api-internal: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:14Z" - latency: 5.388173ms message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 8.322714ms message: 'load-balancer-api-internal: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:14Z" - latency: 4.129658ms message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 7.693235ms message: 'load-balancer-api-internal: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:14Z" - latency: 5.040707ms message: 'load-balancer-api-internal: tcp connection to ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 8.757406ms message: 'load-balancer-api-internal: resolved host name ab688cc9f2e544152a7ce2bb605df621-4f34e7126e589b84.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-132-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "40216" uid: 1be45df8-57f0-4dfc-a946-390f6d519a39 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:28:14Z" message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.017471ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:17:14Z" - latency: 2.111866ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:16:14Z" - latency: 2.492374ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 2.073709ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 2.096015ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 2.070298ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 2.138295ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 1.910628ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:14Z" - latency: 2.138445ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:14Z" - latency: 2.112933ms message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-134-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "40215" uid: e329a6a9-7c8a-44e0-a6b9-d65e90a2e223 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:28:14Z" message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.471µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:17:14Z" - latency: 749.244µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:16:14Z" - latency: 862.298µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 744.179µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 1.044568ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 881.107µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 1.210418ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 1.221134ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:14Z" - latency: 779.92µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:14Z" - latency: 1.377419ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-134-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "40217" uid: 8f609952-0ae3-42e5-b925-ea07de70bae2 spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:28:14Z" message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.15058ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:17:14Z" - latency: 1.866978ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:16:14Z" - latency: 2.005777ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 2.924535ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 1.9786ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 1.897301ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 2.163215ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 2.151433ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:14Z" - latency: 2.249153ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:14Z" - latency: 1.996452ms message: 'network-check-target-ip-10-0-134-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:21:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 0ea33cca-4019-49f3-8925-4b043f8b8f0d resourceVersion: "39081" uid: 4bf6f49c-6c38-4a8d-84d8-0f630380207a spec: sourcePod: network-check-source-8894fc9bd-bg2dl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:27:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 818.926µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:15:14Z" - latency: 1.616006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:15:14Z" - latency: 834.479µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:14Z" - latency: 1.772999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:14Z" - latency: 890.375µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:14Z" - latency: 1.748098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:14Z" - latency: 1.047767ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:14Z" - latency: 1.814482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:14Z" - latency: 981.555µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:14Z" - latency: 1.769145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:14Z" kind: List metadata: resourceVersion: ""