apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "10787" uid: a2d8b116-fac3-4023-ab96-50d55340fca8 spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: 172.31.0.1:443 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "14236" uid: 4c3565b3-9702-452c-aa63-c82eed4df4c1 spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T07:48:56Z" message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.625626ms message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:48:56Z" - latency: 6.137588ms message: 'load-balancer-api-external: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:48:56Z" - latency: 5.25708ms message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:47:56Z" - latency: 8.708503ms message: 'load-balancer-api-external: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:47:56Z" - latency: 4.259329ms message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:46:56Z" - latency: 9.66571ms message: 'load-balancer-api-external: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:46:56Z" - latency: 4.298949ms message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:45:56Z" - latency: 8.302317ms message: 'load-balancer-api-external: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:45:56Z" - latency: 3.638889ms message: 'load-balancer-api-external: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:44:56Z" - latency: 7.716863ms message: 'load-balancer-api-external: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:44:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "14235" uid: 28d29623-5d2d-4165-9c48-3843e1e9d6e4 spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T07:48:56Z" message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.589863ms message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:48:56Z" - latency: 6.238304ms message: 'load-balancer-api-internal: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:48:56Z" - latency: 5.269109ms message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:47:56Z" - latency: 8.77475ms message: 'load-balancer-api-internal: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:47:56Z" - latency: 4.203918ms message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:46:56Z" - latency: 9.690596ms message: 'load-balancer-api-internal: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:46:56Z" - latency: 3.573047ms message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:45:56Z" - latency: 8.321239ms message: 'load-balancer-api-internal: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:45:56Z" - latency: 4.49039ms message: 'load-balancer-api-internal: tcp connection to a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:44:56Z" - latency: 7.761221ms message: 'load-balancer-api-internal: resolved host name a39a7667c6aa2445aad6cdd9a3b99b73-7c5392faa706739f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T07:44:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-network-check-target-ip-10-0-129-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "10785" uid: ad16f160-9ea3-45e5-b046-a8d5639ab3eb spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: 10.134.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-network-check-target-ip-10-0-138-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "10783" uid: 504f760d-4807-48d5-9bee-a97b60941472 spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: 10.132.0.4:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-network-check-target-ip-10-0-142-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "10784" uid: 2968fbec-312c-41df-ad5e-d112c48dd163 spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: 10.133.0.4:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T07:42:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-90-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-90.ec2.internal uid: 17353bfd-f6f5-41c5-b420-7fdd616c13b1 resourceVersion: "14234" uid: 575a58c2-60e2-4aa2-bc2d-67a47eee220d spec: sourcePod: network-check-source-6f8b768455-cqkrf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T07:48:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.801µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:48:56Z" - latency: 1.66323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T07:48:56Z" - latency: 1.114653ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:47:56Z" - latency: 1.953998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T07:47:56Z" - latency: 933.539µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:46:56Z" - latency: 1.843147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T07:46:56Z" - latency: 940.073µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:45:56Z" - latency: 1.694367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T07:45:56Z" - latency: 799.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T07:44:56Z" - latency: 1.783681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T07:44:56Z" kind: List metadata: resourceVersion: ""