apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "44228" uid: eafb9273-6938-49d5-ac2c-844d75b1e260 spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T14:52:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:43Z" - latency: 1.209587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:43Z" - latency: 1.003598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:43Z" - latency: 1.220019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:43Z" - latency: 1.199243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 1.423466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 813.109µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 1.153504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 875.535µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 1.061033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "39969" uid: dbb66bb2-3be5-4e8d-b89d-d65a6ccc4be6 spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T14:51:43Z" message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.771036ms message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 6.183307ms message: 'load-balancer-api-external: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:09:43Z" - latency: 3.851036ms message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 8.40105ms message: 'load-balancer-api-external: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:08:43Z" - latency: 5.474656ms message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 5.962492ms message: 'load-balancer-api-external: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:07:43Z" - latency: 3.837689ms message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 7.368124ms message: 'load-balancer-api-external: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:06:43Z" - latency: 4.714382ms message: 'load-balancer-api-external: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 6.520005ms message: 'load-balancer-api-external: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:05:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "39968" uid: e28c6c91-149e-45ee-8e04-70fde1e3b3a1 spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T14:51:43Z" message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.204709ms message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 6.271095ms message: 'load-balancer-api-internal: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:09:43Z" - latency: 3.801436ms message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 8.446506ms message: 'load-balancer-api-internal: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:08:43Z" - latency: 5.509134ms message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 6.013708ms message: 'load-balancer-api-internal: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:07:43Z" - latency: 3.834388ms message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 7.455015ms message: 'load-balancer-api-internal: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:06:43Z" - latency: 4.722749ms message: 'load-balancer-api-internal: tcp connection to af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 6.449403ms message: 'load-balancer-api-internal: resolved host name af6353c769bb9482dab2570159c0ac19-88990e3f5fbaec91.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T15:05:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-130-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "44225" uid: ca46e764-3727-4e79-9f01-1f91452c64eb spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:52:43Z" message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.985µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:43Z" - latency: 919.177µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:43Z" - latency: 864.762µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:43Z" - latency: 1.60699ms message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:43Z" - latency: 1.236247ms message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 959.602µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 892.366µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 939.689µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 813.65µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 780.322µs message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-132-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "44227" uid: 7e88d974-4c68-4120-a2d6-aa819429268f spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:52:43Z" message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.910369ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:43Z" - latency: 1.83779ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:43Z" - latency: 2.017768ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:43Z" - latency: 1.877041ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:43Z" - latency: 1.807476ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 1.765977ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 1.971604ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 1.671777ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 2.067017ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 2.067091ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-134-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "44226" uid: 1ef3047c-7568-4a1d-9e97-d0500e835745 spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T14:52:43Z" message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.203906ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:13:43Z" - latency: 2.091549ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:12:43Z" - latency: 2.079454ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:11:43Z" - latency: 2.105981ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:10:43Z" - latency: 2.112851ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 2.096905ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 1.935571ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 2.215545ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 2.327555ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 2.099424ms message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:04:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T14:45:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-146-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-146.ec2.internal uid: 329c809e-5e24-4303-bad7-551c61c4e454 resourceVersion: "39967" uid: a21ae09f-73a6-48a8-b6ca-21f54af3a4c5 spec: sourcePod: network-check-source-7f44b6dd87-67bfj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T14:51:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 825.315µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:09:43Z" - latency: 1.81802ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:09:43Z" - latency: 1.272311ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:08:43Z" - latency: 1.76951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:08:43Z" - latency: 877.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:07:43Z" - latency: 1.791518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:07:43Z" - latency: 965.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:06:43Z" - latency: 1.782954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:06:43Z" - latency: 868.037µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T15:05:43Z" - latency: 1.76657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T15:05:43Z" kind: List metadata: resourceVersion: ""