apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "50441" uid: 725a7ae5-c8fc-4767-9783-3294f38f1b98 spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:30:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.252µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 1.306842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 908.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 853.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 1.424843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:54:37Z" - latency: 1.256605ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:53:37Z" - latency: 846.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:52:37Z" - latency: 1.337511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:51:37Z" - latency: 1.039586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:50:37Z" - latency: 906.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "51429" uid: 324f331b-bc94-4d11-9d68-0bc64383c907 spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:29:37Z" message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.929752ms message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:59:37Z" - latency: 8.360026ms message: 'load-balancer-api-external: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:59:37Z" - latency: 3.996568ms message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 8.508614ms message: 'load-balancer-api-external: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:58:37Z" - latency: 3.650538ms message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 8.763623ms message: 'load-balancer-api-external: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:57:37Z" - latency: 4.057585ms message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 8.643474ms message: 'load-balancer-api-external: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:56:37Z" - latency: 4.502996ms message: 'load-balancer-api-external: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 7.474553ms message: 'load-balancer-api-external: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "51430" uid: 9ec61af2-5f44-4bc4-bc77-d1d1467dd744 spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:29:37Z" message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.514508ms message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:59:37Z" - latency: 8.385312ms message: 'load-balancer-api-internal: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:59:37Z" - latency: 3.959601ms message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 8.463419ms message: 'load-balancer-api-internal: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:58:37Z" - latency: 4.30975ms message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 8.837737ms message: 'load-balancer-api-internal: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:57:37Z" - latency: 3.520158ms message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 8.630493ms message: 'load-balancer-api-internal: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:56:37Z" - latency: 4.510008ms message: 'load-balancer-api-internal: tcp connection to abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 7.450161ms message: 'load-balancer-api-internal: resolved host name abfb00fea32ff4114b9ea5c3d04b02fb-4dea6be924703d9b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-130-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "50439" uid: 8d23b4bc-7841-47a2-a65c-273660d9f106 spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:30:37Z" message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.306514ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 2.260657ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 2.404445ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 2.357984ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 2.894803ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:54:37Z" - latency: 2.526913ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:53:37Z" - latency: 2.612873ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:52:37Z" - latency: 2.053234ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:51:37Z" - latency: 2.159481ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:50:37Z" - latency: 2.395628ms message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-131-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "50440" uid: 30608f52-b931-4e93-b6c8-308e04847bad spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:30:37Z" message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.333911ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 2.262437ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 2.360753ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 2.552149ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 2.196314ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:54:37Z" - latency: 2.453826ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:53:37Z" - latency: 2.929489ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:52:37Z" - latency: 2.121347ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:51:37Z" - latency: 2.311021ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:50:37Z" - latency: 2.61976ms message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-142-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "50438" uid: c5546fe2-b9df-492b-aa38-d7bda16224cb spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:30:37Z" message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.415585ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 1.020512ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 1.37206ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 734.73µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 891.747µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:54:37Z" - latency: 1.352402ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:53:37Z" - latency: 930.404µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:52:37Z" - latency: 1.04111ms message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:51:37Z" - latency: 934.937µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:50:37Z" - latency: 952.584µs message: 'network-check-target-ip-10-0-142-103: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:23:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-103.ec2.internal uid: 66a7e1c8-7bde-4e0e-a2e7-182911255145 resourceVersion: "51428" uid: 51efc971-a09a-454c-b35a-82e153aae085 spec: sourcePod: network-check-source-dbd9cf844-682l7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:29:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.899µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:59:37Z" - latency: 1.79911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:59:37Z" - latency: 821.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:58:37Z" - latency: 1.697726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:58:37Z" - latency: 954.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:57:37Z" - latency: 2.596566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:57:37Z" - latency: 837.038µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:56:37Z" - latency: 2.087906ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:56:37Z" - latency: 1.184106ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:55:37Z" - latency: 1.511609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:55:37Z" kind: List metadata: resourceVersion: ""