apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "79107" uid: 03ce8808-710a-449f-b773-78a060554ff8 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T20:38:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.213243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:27:36Z" - latency: 1.513393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:26:36Z" - latency: 1.345292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 883.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 1.268077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 870.733µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 1.195129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 1.082288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:20:36Z" - latency: 1.13972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:19:36Z" - latency: 1.431159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "76977" uid: 087d1b2c-92d9-480c-8477-e8f8b0a3f6a5 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T20:37:36Z" message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.690666ms message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 8.213778ms message: 'load-balancer-api-external: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:25:36Z" - latency: 3.784298ms message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 6.950204ms message: 'load-balancer-api-external: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:24:36Z" - latency: 5.55762ms message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 7.486919ms message: 'load-balancer-api-external: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:23:36Z" - latency: 4.467741ms message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 6.606571ms message: 'load-balancer-api-external: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:22:36Z" - latency: 3.541673ms message: 'load-balancer-api-external: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 7.051602ms message: 'load-balancer-api-external: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:21:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "76978" uid: f6308248-5885-48dd-b67e-eb3a692bee05 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T20:37:36Z" message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.731165ms message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 8.096219ms message: 'load-balancer-api-internal: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:25:36Z" - latency: 3.427168ms message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 6.901508ms message: 'load-balancer-api-internal: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:24:36Z" - latency: 3.604335ms message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 7.526267ms message: 'load-balancer-api-internal: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:23:36Z" - latency: 4.510321ms message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 6.542871ms message: 'load-balancer-api-internal: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:22:36Z" - latency: 4.912528ms message: 'load-balancer-api-internal: tcp connection to a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 7.01113ms message: 'load-balancer-api-internal: resolved host name a413ef6c91de24d4188712cdbf334a24-c52487293f8ca3d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:21:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-134-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "79104" uid: 6e978137-db74-4751-ba75-6b798979cb16 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T20:38:36Z" message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072257ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:27:36Z" - latency: 1.973777ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:26:36Z" - latency: 1.948889ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 1.861912ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 2.322195ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 2.039834ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 2.308082ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 2.466629ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:20:36Z" - latency: 2.211189ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:19:36Z" - latency: 2.55616ms message: 'network-check-target-ip-10-0-134-148: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-139-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "79106" uid: c41b0454-c0dc-47be-ab5a-ea90cc6f1cd0 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T20:38:36Z" message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.054856ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:27:36Z" - latency: 2.215972ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:26:36Z" - latency: 2.111381ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 2.176513ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 1.952896ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 1.850857ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 2.201481ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 2.093406ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:20:36Z" - latency: 2.130827ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:19:36Z" - latency: 2.675293ms message: 'network-check-target-ip-10-0-139-183: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-network-check-target-ip-10-0-142-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "79105" uid: 05ddeab9-c3f9-4ac8-9e95-f9f912997aaa spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T20:38:36Z" message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.316637ms message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:27:36Z" - latency: 850.797µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:26:36Z" - latency: 1.095579ms message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 912.202µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 1.064188ms message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 774.521µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 962.672µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 805.535µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:20:36Z" - latency: 1.13683ms message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:19:36Z" - latency: 764.201µs message: 'network-check-target-ip-10-0-142-69: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:18:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T20:31:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-69-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-69.ec2.internal uid: 58c4161e-1386-45be-86e1-8f5232ce943d resourceVersion: "76976" uid: 922c31ab-cdeb-4b72-b6c0-36d2e494de08 spec: sourcePod: network-check-source-65bdbbff45-pdm2k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T20:37:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.55µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:25:36Z" - latency: 2.07606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:25:36Z" - latency: 1.059401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:24:36Z" - latency: 2.178872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:24:36Z" - latency: 1.091562ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:23:36Z" - latency: 1.986832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:23:36Z" - latency: 772.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:22:36Z" - latency: 2.155377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:22:36Z" - latency: 850.409µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:21:36Z" - latency: 1.798773ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:21:36Z" kind: List metadata: resourceVersion: ""