apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51047" uid: ef855966-236d-49a1-976b-62decf736ae2 spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-31T21:38:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 907.974µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 1.170692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 1.034813ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 1.629798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:02:50Z" - latency: 1.206693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:01:50Z" - latency: 1.655424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:00:50Z" - latency: 1.21797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:59:50Z" - latency: 1.814679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:58:50Z" - latency: 1.225402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:57:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51663" uid: 934d39be-1f9b-4878-8467-a4dc89a44753 spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T21:37:50Z" message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.568206ms message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:07:50Z" - latency: 7.779624ms message: 'load-balancer-api-external: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:07:50Z" - latency: 5.497779ms message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 7.079493ms message: 'load-balancer-api-external: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:06:50Z" - latency: 4.983352ms message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 6.786424ms message: 'load-balancer-api-external: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:05:50Z" - latency: 4.581168ms message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 7.461384ms message: 'load-balancer-api-external: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:04:50Z" - latency: 3.684214ms message: 'load-balancer-api-external: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 7.401057ms message: 'load-balancer-api-external: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:03:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51662" uid: b3d12055-3571-432a-9a15-4eea640ee94c spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-31T21:37:50Z" message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.552829ms message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:07:50Z" - latency: 7.870725ms message: 'load-balancer-api-internal: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:07:50Z" - latency: 5.484086ms message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 7.185554ms message: 'load-balancer-api-internal: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:06:50Z" - latency: 4.975202ms message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 6.887827ms message: 'load-balancer-api-internal: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:05:50Z" - latency: 4.552101ms message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 7.66321ms message: 'load-balancer-api-internal: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:04:50Z" - latency: 3.847834ms message: 'load-balancer-api-internal: tcp connection to ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 7.36905ms message: 'load-balancer-api-internal: resolved host name ac68da4c9abca4cc5adf18a2a02ad02d-3969653f6c9c584e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-31T22:03:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-134-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51045" uid: cd996da7-2b6a-4d6e-8d1c-242717b85446 spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:38:50Z" message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.098421ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 2.442018ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 2.53588ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 2.419282ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 2.263344ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:02:50Z" - latency: 2.747541ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:01:50Z" - latency: 2.925649ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:00:50Z" - latency: 2.552446ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:59:50Z" - latency: 2.526959ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:58:50Z" - latency: 2.412844ms message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:57:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-135-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51044" uid: 9246589b-1a01-4d12-8ffc-9f65db679ddb spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:38:50Z" message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.425µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 927.69µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 1.214228ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 936.717µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 999.409µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:02:50Z" - latency: 877.252µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:01:50Z" - latency: 861.616µs message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:00:50Z" - latency: 1.533649ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:59:50Z" - latency: 1.011888ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:58:50Z" - latency: 1.353813ms message: 'network-check-target-ip-10-0-135-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:57:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-ip-10-0-140-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51046" uid: 0beb63fc-7f39-4746-9304-de474324316b spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-31T21:38:50Z" message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.384325ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 2.458259ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 2.388216ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 2.41372ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 2.362717ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:02:50Z" - latency: 2.445237ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:01:50Z" - latency: 2.335255ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:00:50Z" - latency: 2.531496ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:59:50Z" - latency: 2.233548ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:58:50Z" - latency: 2.365174ms message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-31T21:57:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-31T21:31:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-32.ec2.internal uid: 8267cf6e-9759-4926-9527-4567b5bec985 resourceVersion: "51661" uid: 31ee454d-628a-4e01-9e8a-4c329271084d spec: sourcePod: network-check-source-65bdbbff45-9qpb6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-31T21:37:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 806.493µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:07:50Z" - latency: 1.854015ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:07:50Z" - latency: 1.176957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:06:50Z" - latency: 2.030863ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:06:50Z" - latency: 944.699µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:05:50Z" - latency: 1.703688ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:05:50Z" - latency: 1.020064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:04:50Z" - latency: 1.67235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:04:50Z" - latency: 1.003641ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-31T22:03:50Z" - latency: 1.87051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-31T22:03:50Z" kind: List metadata: resourceVersion: ""