apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "25428" uid: 753632ba-5ce8-4089-a906-e8cdcc5b366a spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T12:44:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.251543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 975.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 935.204µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 1.127631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:02:51Z" - latency: 933.289µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:01:51Z" - latency: 931.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:00:51Z" - latency: 914.529µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:59:51Z" - latency: 1.027322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:58:51Z" - latency: 1.729693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:57:51Z" - latency: 1.018825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "26406" uid: 63bbcee4-ac7e-44d5-b713-cb8c60ba380e spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:43:51Z" message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.331195ms message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:07:51Z" - latency: 7.074193ms message: 'load-balancer-api-external: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:07:51Z" - latency: 5.046219ms message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:06:51Z" - latency: 8.783203ms message: 'load-balancer-api-external: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:06:51Z" - latency: 4.787971ms message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 8.262352ms message: 'load-balancer-api-external: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:05:51Z" - latency: 5.861391ms message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 8.28497ms message: 'load-balancer-api-external: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:04:51Z" - latency: 4.848681ms message: 'load-balancer-api-external: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 9.6149ms message: 'load-balancer-api-external: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "26405" uid: 23b7b598-4366-410f-9519-a1aeb48efdff spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T12:43:51Z" message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.343045ms message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:07:51Z" - latency: 7.016096ms message: 'load-balancer-api-internal: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:07:51Z" - latency: 5.090377ms message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:06:51Z" - latency: 8.734684ms message: 'load-balancer-api-internal: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:06:51Z" - latency: 3.394486ms message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 8.135792ms message: 'load-balancer-api-internal: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:05:51Z" - latency: 5.928908ms message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 8.263843ms message: 'load-balancer-api-internal: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:04:51Z" - latency: 4.829907ms message: 'load-balancer-api-internal: tcp connection to ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 9.578917ms message: 'load-balancer-api-internal: resolved host name ad17baa2948ef4229891885387f1c6a5-94c3ef8723e82abe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:03:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-132-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "25427" uid: 9a6648d6-5cf5-4848-a92c-de4f5914acd1 spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:44:51Z" message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.591713ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 2.38271ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 2.347396ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 2.336203ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:02:51Z" - latency: 2.219141ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:01:51Z" - latency: 2.470828ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:00:51Z" - latency: 2.75755ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:59:51Z" - latency: 2.521588ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:58:51Z" - latency: 1.933372ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:57:51Z" - latency: 2.627484ms message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-138-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "25425" uid: c9c121e5-2e9c-467b-9cfe-7136756d0653 spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:44:51Z" message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.819238ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 839.74µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 1.250706ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 897.684µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:02:51Z" - latency: 868.154µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:01:51Z" - latency: 790.41µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:00:51Z" - latency: 934.852µs message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:59:51Z" - latency: 1.508811ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:58:51Z" - latency: 1.096095ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:57:51Z" - latency: 1.624116ms message: 'network-check-target-ip-10-0-138-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-ip-10-0-142-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "25426" uid: bde54de0-1233-49e4-b763-4d5c16f575c7 spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T12:44:51Z" message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.621702ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 2.674032ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 2.559346ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 2.602893ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:02:51Z" - latency: 2.240732ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:01:51Z" - latency: 2.388496ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:00:51Z" - latency: 2.521597ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:59:51Z" - latency: 2.71132ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:58:51Z" - latency: 2.824193ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:57:51Z" - latency: 2.464676ms message: 'network-check-target-ip-10-0-142-139: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T12:56:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:37:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-58.ec2.internal uid: 28a0c283-151b-41f0-95bb-c5613e5d2ce8 resourceVersion: "26404" uid: 5939532d-7238-4fcc-828e-feb445bf4af9 spec: sourcePod: network-check-source-7d88cb55d8-nqdtk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T12:43:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:07:51Z" - latency: 2.182997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:07:51Z" - latency: 1.08764ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:06:51Z" - latency: 1.572132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:06:51Z" - latency: 1.110838ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:05:51Z" - latency: 2.098666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:05:51Z" - latency: 925.018µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:04:51Z" - latency: 1.611306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:04:51Z" - latency: 1.399173ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:03:51Z" - latency: 1.947302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:03:51Z" kind: List metadata: resourceVersion: ""