apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "31517" uid: 159a88a7-f144-49fc-9b9b-cda66ac5be93 spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T10:03:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:10:37Z" - latency: 1.053583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:37Z" - latency: 1.088911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 820.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 1.0043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 935.356µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 882.553µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 860.969µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:37Z" - latency: 916.185µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:37Z" - latency: 1.283224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "29633" uid: eed181c9-3045-4cf3-9aa4-668d42b991ae spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T10:02:37Z" message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.81201ms message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 6.278047ms message: 'load-balancer-api-external: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:37Z" - latency: 4.593625ms message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 7.233848ms message: 'load-balancer-api-external: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:37Z" - latency: 5.1383ms message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 7.165977ms message: 'load-balancer-api-external: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:37Z" - latency: 5.073689ms message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 7.059587ms message: 'load-balancer-api-external: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:37Z" - latency: 4.93822ms message: 'load-balancer-api-external: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 7.494757ms message: 'load-balancer-api-external: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "29632" uid: 7e888501-edca-440c-bc13-642f18743769 spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T10:02:37Z" message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.801043ms message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 6.321152ms message: 'load-balancer-api-internal: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:37Z" - latency: 4.568503ms message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 7.283748ms message: 'load-balancer-api-internal: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:37Z" - latency: 5.066499ms message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 7.209401ms message: 'load-balancer-api-internal: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:37Z" - latency: 5.017817ms message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 7.164664ms message: 'load-balancer-api-internal: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:37Z" - latency: 4.941043ms message: 'load-balancer-api-internal: tcp connection to a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 7.560992ms message: 'load-balancer-api-internal: resolved host name a8fd1154b31714abd96a79a4f8c56ba6-e9455cd6a31bf37a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:04:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-136-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "31515" uid: e5e0c7d1-f1ef-43e7-b1e7-6d8fa602b6ca spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T10:03:37Z" message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.588971ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:10:37Z" - latency: 2.239123ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:37Z" - latency: 2.330881ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 1.961207ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 2.625299ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 2.441404ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 2.7436ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 2.310043ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:37Z" - latency: 2.204472ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:37Z" - latency: 2.988958ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-138-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "31514" uid: c1228675-c89b-45c1-aa6f-d21b5b295e91 spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T10:03:37Z" message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.419738ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:10:37Z" - latency: 2.155459ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:37Z" - latency: 2.372858ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 2.063062ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 2.099372ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 2.044737ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 2.454516ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 1.957293ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:37Z" - latency: 2.284322ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:37Z" - latency: 2.344917ms message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-139-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "31513" uid: fc9dfa0d-7065-4b7a-9e8b-37f6a93c5528 spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T10:03:37Z" message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.597µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:10:37Z" - latency: 915.811µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:37Z" - latency: 841.498µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 854.952µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 1.595268ms message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 918.331µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 989.19µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 866.345µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:37Z" - latency: 777.207µs message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:37Z" - latency: 1.734223ms message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:56:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-37.ec2.internal uid: 3dd9a9ca-de03-4417-ac94-9c4ec018cf09 resourceVersion: "29631" uid: 54f5e1bf-6d89-40cf-b174-ab23646972cb spec: sourcePod: network-check-source-dbd9cf844-md722 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T10:02:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 938.414µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:37Z" - latency: 1.62599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:37Z" - latency: 820.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:37Z" - latency: 1.931011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:37Z" - latency: 1.235064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:37Z" - latency: 1.736801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:37Z" - latency: 1.107259ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:37Z" - latency: 1.958491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:37Z" - latency: 1.008065ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:37Z" - latency: 1.768953ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:04:37Z" kind: List metadata: resourceVersion: ""