apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "30402" uid: 6ff89fc4-f334-40d6-971b-61835174ec4d spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T17:30:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.153052ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:37:00Z" - latency: 1.104966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:36:00Z" - latency: 919.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 1.265741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 1.590918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 1.188111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 875.06µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 1.020976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:30:00Z" - latency: 842.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:29:00Z" - latency: 1.666118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:28:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "29102" uid: 470bad3b-c41a-4f99-a40d-9faf8fc05355 spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T17:29:00Z" message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.560726ms message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 8.505627ms message: 'load-balancer-api-external: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:35:00Z" - latency: 4.950094ms message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 8.360626ms message: 'load-balancer-api-external: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:34:00Z" - latency: 4.972321ms message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 9.443452ms message: 'load-balancer-api-external: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:33:00Z" - latency: 6.392568ms message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 9.015763ms message: 'load-balancer-api-external: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:32:00Z" - latency: 6.193435ms message: 'load-balancer-api-external: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 8.452515ms message: 'load-balancer-api-external: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:31:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "29101" uid: 2fd68466-25d9-4b65-9e5e-12f72de16910 spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T17:29:00Z" message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.386249ms message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 8.598949ms message: 'load-balancer-api-internal: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:35:00Z" - latency: 4.939454ms message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 8.312728ms message: 'load-balancer-api-internal: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:34:00Z" - latency: 4.358242ms message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 9.509983ms message: 'load-balancer-api-internal: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:33:00Z" - latency: 6.332083ms message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 9.113317ms message: 'load-balancer-api-internal: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:32:00Z" - latency: 6.15428ms message: 'load-balancer-api-internal: tcp connection to ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 8.502645ms message: 'load-balancer-api-internal: resolved host name ac756dd7bf8a2429d83675fa60d08f82-c0c97cd369ec14e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T17:31:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-network-check-target-ip-10-0-132-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "30400" uid: 71bdb7c8-418e-41ca-ab88-667ec5694174 spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T17:30:00Z" message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138689ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:37:00Z" - latency: 1.932089ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:36:00Z" - latency: 2.329429ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 2.229142ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 2.166147ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 2.779709ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 2.058409ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 2.053359ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:30:00Z" - latency: 1.997783ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:29:00Z" - latency: 2.629836ms message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:28:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-network-check-target-ip-10-0-133-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "30399" uid: 62512bf6-980e-4674-86ba-86d614b574df spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T17:30:00Z" message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061897ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:37:00Z" - latency: 915.215µs message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:36:00Z" - latency: 1.522777ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 1.470907ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 944.999µs message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 1.322845ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 897.918µs message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 1.225978ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:30:00Z" - latency: 1.22124ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:29:00Z" - latency: 1.359721ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:28:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-network-check-target-ip-10-0-142-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "30401" uid: 9dd05966-92ce-40f2-b494-417a90f86e76 spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T17:30:00Z" message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.593067ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:37:00Z" - latency: 2.290535ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:36:00Z" - latency: 2.354853ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 2.729563ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 2.843207ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 2.692203ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 2.505926ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 2.795251ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:30:00Z" - latency: 2.875527ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:29:00Z" - latency: 2.457016ms message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:28:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T17:22:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-125.ec2.internal uid: 17174ac5-93e8-4eef-b228-3c2f4dd74c7e resourceVersion: "29100" uid: 722a6093-e337-4597-9689-d0129474950c spec: sourcePod: network-check-source-dbd9cf844-ksbhq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T17:29:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 837.115µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:35:00Z" - latency: 2.243742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T17:35:00Z" - latency: 947.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:34:00Z" - latency: 1.950675ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T17:34:00Z" - latency: 1.063435ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:33:00Z" - latency: 2.011885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T17:33:00Z" - latency: 1.168976ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:32:00Z" - latency: 1.825377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T17:32:00Z" - latency: 922.243µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T17:31:00Z" - latency: 2.067513ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T17:31:00Z" kind: List metadata: resourceVersion: ""