apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "68348" uid: 5a423463-def9-49f4-94d1-bac2663c7f42 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T11:08:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.871µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:50:06Z" - latency: 1.217815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 952.507µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 1.401684ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 1.093637ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 2.649521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 1.030945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:44:06Z" - latency: 733.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:43:06Z" - latency: 1.246408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:42:06Z" - latency: 1.217156ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:41:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "67331" uid: 24c43c9d-0f23-4a97-bc84-e91eef14c684 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T11:07:06Z" message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.068811ms message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 7.128779ms message: 'load-balancer-api-external: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:49:06Z" - latency: 4.871118ms message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 6.111303ms message: 'load-balancer-api-external: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:48:06Z" - latency: 4.408983ms message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 6.873396ms message: 'load-balancer-api-external: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:47:06Z" - latency: 5.979148ms message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 6.732167ms message: 'load-balancer-api-external: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:46:06Z" - latency: 4.438854ms message: 'load-balancer-api-external: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 9.626743ms message: 'load-balancer-api-external: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:45:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "67332" uid: dd9d5bf0-c57b-4b35-bbf5-3cf9e0d77216 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T11:07:06Z" message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.846572ms message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 7.030071ms message: 'load-balancer-api-internal: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:49:06Z" - latency: 4.889944ms message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 6.061219ms message: 'load-balancer-api-internal: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:48:06Z" - latency: 4.690471ms message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 6.770121ms message: 'load-balancer-api-internal: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:47:06Z" - latency: 4.472963ms message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 6.657853ms message: 'load-balancer-api-internal: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:46:06Z" - latency: 4.480563ms message: 'load-balancer-api-internal: tcp connection to ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 9.384819ms message: 'load-balancer-api-internal: resolved host name ac2e7d5a9295f4a9b9efd39fa0d5d3f6-50287abf00f72a97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T11:45:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-network-check-target-ip-10-0-131-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "68347" uid: 524cf4a1-7df5-4085-87b1-7894520d8a95 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T11:08:06Z" message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.125921ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:50:06Z" - latency: 2.259205ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 2.045092ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 1.974435ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 1.852685ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 3.483392ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 2.217712ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:44:06Z" - latency: 1.803596ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:43:06Z" - latency: 2.477229ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:42:06Z" - latency: 1.802564ms message: 'network-check-target-ip-10-0-131-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:41:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-network-check-target-ip-10-0-134-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "68345" uid: ac819001-5940-4137-85d7-4c3eec855113 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T11:08:06Z" message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117842ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:50:06Z" - latency: 990.98µs message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 1.334658ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 779.06µs message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 1.094729ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 3.972225ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 938.583µs message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:44:06Z" - latency: 841.577µs message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:43:06Z" - latency: 935.42µs message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:42:06Z" - latency: 1.387814ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:41:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-network-check-target-ip-10-0-140-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "68346" uid: 2cc5fcca-4b4a-45c2-a5d5-6ec7e9648527 spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T11:08:06Z" message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.558641ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:50:06Z" - latency: 2.326374ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 2.066266ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 2.039124ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 1.963659ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 4.931113ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 2.392854ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:44:06Z" - latency: 2.075995ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:43:06Z" - latency: 2.349414ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:42:06Z" - latency: 2.118206ms message: 'network-check-target-ip-10-0-140-233: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:41:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T11:01:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-138.ec2.internal uid: 2c97c369-7660-4539-8057-2f0592a5d0d4 resourceVersion: "67330" uid: 6194791c-f729-4059-937d-7f9d5ea5bc9a spec: sourcePod: network-check-source-7bc5b6bf85-5b4gd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T11:07:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123373ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:49:06Z" - latency: 2.122401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T11:49:06Z" - latency: 1.074923ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:48:06Z" - latency: 1.624771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T11:48:06Z" - latency: 924.278µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:47:06Z" - latency: 1.938025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T11:47:06Z" - latency: 892.108µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:46:06Z" - latency: 1.926373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T11:46:06Z" - latency: 2.012295ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T11:45:06Z" - latency: 3.586069ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T11:45:06Z" kind: List metadata: resourceVersion: ""