apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "45236" uid: 23191540-a739-4c60-ad07-8b8ce2f9ca0d spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T13:03:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.422098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 949.782µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 911.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 845.283µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:56Z" - latency: 1.048305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:56Z" - latency: 1.093926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:56Z" - latency: 1.114936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:56Z" - latency: 945.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:56Z" - latency: 857.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:56Z" - latency: 1.304876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "47289" uid: d9b1ec21-83b1-4d4b-8ddf-019712d174e5 spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:02:56Z" message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.308344ms message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:56Z" - latency: 6.984953ms message: 'load-balancer-api-external: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:56Z" - latency: 5.081215ms message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:56Z" - latency: 6.724581ms message: 'load-balancer-api-external: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:25:56Z" - latency: 4.765797ms message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 6.751824ms message: 'load-balancer-api-external: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:24:56Z" - latency: 5.094889ms message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 6.803826ms message: 'load-balancer-api-external: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:23:56Z" - latency: 6.379134ms message: 'load-balancer-api-external: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 6.640105ms message: 'load-balancer-api-external: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "47288" uid: ec7e7383-7502-44cd-9338-c2f9134fe022 spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:02:56Z" message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.354958ms message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:56Z" - latency: 6.884665ms message: 'load-balancer-api-internal: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:56Z" - latency: 5.292062ms message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:56Z" - latency: 6.629573ms message: 'load-balancer-api-internal: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:25:56Z" - latency: 4.79071ms message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 6.658988ms message: 'load-balancer-api-internal: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:24:56Z" - latency: 7.342788ms message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 6.714771ms message: 'load-balancer-api-internal: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:23:56Z" - latency: 4.259018ms message: 'load-balancer-api-internal: tcp connection to ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 6.698043ms message: 'load-balancer-api-internal: resolved host name ae100ee5a631a4da2a2681c2e3f8d953-01c00a6b34d5e66a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-128-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "45234" uid: 4f0ed581-a61c-4ecb-8840-90ada143336b spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:03:56Z" message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.656609ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 1.971198ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 1.719621ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 1.829444ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:56Z" - latency: 2.088648ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:56Z" - latency: 2.119334ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:56Z" - latency: 2.217798ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:56Z" - latency: 1.710378ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:56Z" - latency: 2.019222ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:56Z" - latency: 2.161564ms message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-128-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "45235" uid: b5db6148-edfe-4302-8b79-6df27a0b1eec spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:03:56Z" message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.52606ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 2.284567ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 2.022781ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 2.268706ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:56Z" - latency: 2.231179ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:56Z" - latency: 2.396125ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:56Z" - latency: 2.602222ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:56Z" - latency: 2.362074ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:56Z" - latency: 2.456203ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:56Z" - latency: 2.268207ms message: 'network-check-target-ip-10-0-128-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-ip-10-0-129-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "45233" uid: 4d5a5f58-921a-438a-8166-8b233e674b83 spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:03:56Z" message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.095µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 867.562µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 751.273µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 971.268µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:21:56Z" - latency: 1.506763ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:20:56Z" - latency: 859.87µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:19:56Z" - latency: 876.345µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:18:56Z" - latency: 818.574µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:17:56Z" - latency: 1.001684ms message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:16:56Z" - latency: 910.824µs message: 'network-check-target-ip-10-0-129-16: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:15:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:56:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-16.ec2.internal uid: b1ec99df-6f91-46ca-b74a-afdb208aa65f resourceVersion: "47287" uid: fb2e7776-b4ed-494c-bbe7-cc35b39ada24 spec: sourcePod: network-check-source-dbd9cf844-x8kjc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T13:02:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.0839ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:56Z" - latency: 1.863644ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:56Z" - latency: 843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:56Z" - latency: 1.964459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:25:56Z" - latency: 940.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:24:56Z" - latency: 1.775798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:24:56Z" - latency: 843.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:23:56Z" - latency: 1.931177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:23:56Z" - latency: 831.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:22:56Z" - latency: 1.749924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:22:56Z" kind: List metadata: resourceVersion: ""