apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32020" uid: 5380ee26-4bba-431a-a62c-4dcf2a411283 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T15:49:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.516µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 937.008µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 1.232178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 964.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 921.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 979.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:19:41Z" - latency: 939.5µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:18:41Z" - latency: 891.382µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:17:41Z" - latency: 962.192µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:16:41Z" - latency: 835.421µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:15:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32022" uid: 7abb99f5-9fbd-47ef-8e3b-f6fc00fc1161 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T15:48:41Z" message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.860126ms message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 7.184307ms message: 'load-balancer-api-external: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:24:41Z" - latency: 3.983481ms message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 8.031198ms message: 'load-balancer-api-external: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:23:41Z" - latency: 3.14565ms message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 10.294452ms message: 'load-balancer-api-external: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:22:41Z" - latency: 4.337017ms message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 8.600527ms message: 'load-balancer-api-external: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:21:41Z" - latency: 4.699637ms message: 'load-balancer-api-external: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 8.259625ms message: 'load-balancer-api-external: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:20:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32021" uid: e62edaa4-2ed7-4baf-99da-ec92dc2d5201 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T15:48:41Z" message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.83097ms message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 7.125144ms message: 'load-balancer-api-internal: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:24:41Z" - latency: 3.986297ms message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 7.881285ms message: 'load-balancer-api-internal: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:23:41Z" - latency: 4.609555ms message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 10.327779ms message: 'load-balancer-api-internal: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:22:41Z" - latency: 4.686629ms message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 8.646686ms message: 'load-balancer-api-internal: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:21:41Z" - latency: 4.692777ms message: 'load-balancer-api-internal: tcp connection to aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 8.296618ms message: 'load-balancer-api-internal: resolved host name aa2c19a37253f4dfcb05d8d75a4658c3-3b1fe42532b88050.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T16:20:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-network-check-target-ip-10-0-128-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32016" uid: 661c1df7-fb14-45be-b919-a30dae958067 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T15:49:41Z" message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.315574ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 2.294998ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 2.569176ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 2.315148ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 2.31907ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 2.385652ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:19:41Z" - latency: 2.387653ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:18:41Z" - latency: 2.086465ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:17:41Z" - latency: 2.222532ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:16:41Z" - latency: 2.266154ms message: 'network-check-target-ip-10-0-128-116: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:15:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-network-check-target-ip-10-0-132-207 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32015" uid: 26b92273-c364-4206-b66f-95b6edeec3e9 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T15:49:41Z" message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.295287ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 948.914µs message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 856.678µs message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 934.015µs message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 944.149µs message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 1.028714ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:19:41Z" - latency: 1.015627ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:18:41Z" - latency: 976.732µs message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:17:41Z" - latency: 1.091726ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:16:41Z" - latency: 1.368011ms message: 'network-check-target-ip-10-0-132-207: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:15:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-network-check-target-ip-10-0-140-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32018" uid: 6f22cdec-11c4-4ebc-b740-e0dc631ede52 spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T15:49:41Z" message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.33858ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 2.319691ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 2.449824ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 2.014879ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 2.451721ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 2.17306ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:19:41Z" - latency: 2.236572ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:18:41Z" - latency: 2.487267ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:17:41Z" - latency: 2.627982ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:16:41Z" - latency: 2.650998ms message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:15:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T15:42:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-207-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-207.ec2.internal uid: c87c3a11-b0b6-4cc5-a739-af83b92f692e resourceVersion: "32017" uid: 1aa6e09e-76b6-42e2-a5f1-67d8133d7b3c spec: sourcePod: network-check-source-6f8b768455-kjss7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T15:48:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.820129ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:24:41Z" - latency: 1.760168ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T16:24:41Z" - latency: 987.081µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:23:41Z" - latency: 1.812832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T16:23:41Z" - latency: 881.504µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:22:41Z" - latency: 1.984078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T16:22:41Z" - latency: 882.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:21:41Z" - latency: 1.723383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T16:21:41Z" - latency: 1.353257ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T16:20:41Z" - latency: 1.679189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T16:20:41Z" kind: List metadata: resourceVersion: ""