apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "71127" uid: 05b9d671-bbff-42ef-b1b3-6c4ac4b217d2 spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T02:45:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.217247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:27:47Z" - latency: 1.236264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 1.108304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 1.222058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 1.24474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 1.011664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 1.270101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:21:47Z" - latency: 1.169284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:20:47Z" - latency: 1.206172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:19:47Z" - latency: 1.120671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:18:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "70334" uid: 4fe97be0-1f90-4459-befb-a9d6853cf749 spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T02:44:47Z" message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.993719ms message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 7.204001ms message: 'load-balancer-api-external: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:26:47Z" - latency: 3.265766ms message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 7.343875ms message: 'load-balancer-api-external: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:25:47Z" - latency: 4.105596ms message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 8.317045ms message: 'load-balancer-api-external: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:24:47Z" - latency: 3.288602ms message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 7.546564ms message: 'load-balancer-api-external: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:23:47Z" - latency: 4.038001ms message: 'load-balancer-api-external: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 7.458945ms message: 'load-balancer-api-external: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "70335" uid: 5ca55bbe-2c6a-4c75-a902-fe7d9e47a7bb spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T02:44:47Z" message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.987173ms message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 7.173134ms message: 'load-balancer-api-internal: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:26:47Z" - latency: 3.30451ms message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 7.292627ms message: 'load-balancer-api-internal: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:25:47Z" - latency: 4.170036ms message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 8.24815ms message: 'load-balancer-api-internal: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:24:47Z" - latency: 3.312355ms message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 7.453797ms message: 'load-balancer-api-internal: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:23:47Z" - latency: 4.099022ms message: 'load-balancer-api-internal: tcp connection to aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 7.383179ms message: 'load-balancer-api-internal: resolved host name aac37c58620564a01ae4ca5e88cf6158-ba00143535e8ae18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T03:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-133-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "71124" uid: 306d54c4-63e9-481c-9370-5107592b5837 spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T02:45:47Z" message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.392978ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:27:47Z" - latency: 1.03607ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 1.174963ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 996.918µs message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 1.089458ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 1.691178ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 920.454µs message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:21:47Z" - latency: 1.060709ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:20:47Z" - latency: 1.148066ms message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:19:47Z" - latency: 991.898µs message: 'network-check-target-ip-10-0-133-22: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:18:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-134-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "71126" uid: 0b48440b-99dc-4233-b18d-5c14f2651f0e spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T02:45:47Z" message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.433981ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:27:47Z" - latency: 1.96359ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 2.118914ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 2.202531ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 2.312914ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 2.075567ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 2.256957ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:21:47Z" - latency: 2.631012ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:20:47Z" - latency: 2.640559ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:19:47Z" - latency: 2.021841ms message: 'network-check-target-ip-10-0-134-184: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:18:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-ip-10-0-141-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "71125" uid: 86a1d344-6f5e-446d-b8b6-ff7527ba6540 spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T02:45:47Z" message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.45544ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:27:47Z" - latency: 2.317898ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 2.4568ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 2.576213ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 2.341927ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 2.529064ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 2.437913ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:21:47Z" - latency: 2.322988ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:20:47Z" - latency: 2.668469ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:19:47Z" - latency: 2.343717ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:18:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T02:38:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-22-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-22.ec2.internal uid: 20315249-497c-4adf-8b5c-a3535744e6e5 resourceVersion: "70333" uid: ab50b918-5882-4831-8d5a-528f60b434d5 spec: sourcePod: network-check-source-7d88cb55d8-2xfbq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T02:44:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.098873ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:26:47Z" - latency: 1.910614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T03:26:47Z" - latency: 1.256207ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:25:47Z" - latency: 1.886181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T03:25:47Z" - latency: 943.006µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:24:47Z" - latency: 1.989645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T03:24:47Z" - latency: 1.05446ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:23:47Z" - latency: 2.001273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T03:23:47Z" - latency: 1.044349ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T03:22:47Z" - latency: 2.07886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T03:22:47Z" kind: List metadata: resourceVersion: ""