apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "18430" uid: 265b9c5f-f151-4cc9-92c9-06d39150dc21 spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T14:27:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 1.275734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:00Z" - latency: 1.119385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:00Z" - latency: 1.013594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:00Z" - latency: 1.004532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:30:00Z" - latency: 980.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:29:00Z" - latency: 850.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:28:00Z" - latency: 1.191705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:27:00Z" - latency: 1.05974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:26:00Z" - latency: 906.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:25:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "20469" uid: 5aa2e430-22f2-4fd1-b377-a03645e4912c spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T14:26:00Z" message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.681787ms message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:00Z" - latency: 6.750683ms message: 'load-balancer-api-external: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:38:00Z" - latency: 5.051102ms message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:00Z" - latency: 7.426873ms message: 'load-balancer-api-external: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:37:00Z" - latency: 4.421138ms message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:00Z" - latency: 6.974049ms message: 'load-balancer-api-external: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:36:00Z" - latency: 4.333537ms message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:00Z" - latency: 6.363524ms message: 'load-balancer-api-external: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:35:00Z" - latency: 4.309983ms message: 'load-balancer-api-external: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 9.167072ms message: 'load-balancer-api-external: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:34:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "20470" uid: 50269f7e-fdb5-4475-9c6c-2adaa7965c7c spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T14:26:00Z" message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.316066ms message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:00Z" - latency: 6.852951ms message: 'load-balancer-api-internal: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:38:00Z" - latency: 4.993472ms message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:00Z" - latency: 7.488036ms message: 'load-balancer-api-internal: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:37:00Z" - latency: 4.410404ms message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:00Z" - latency: 7.170951ms message: 'load-balancer-api-internal: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:36:00Z" - latency: 4.296706ms message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:00Z" - latency: 6.477426ms message: 'load-balancer-api-internal: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:35:00Z" - latency: 4.290781ms message: 'load-balancer-api-internal: tcp connection to ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 9.332517ms message: 'load-balancer-api-internal: resolved host name ab8fc599cb9964a589906ed011a5ce56-48482642e285ae6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T14:34:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-129-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "18429" uid: 249af502-623e-4b4f-8577-5d8dd3636158 spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:27:00Z" message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.272437ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 2.490767ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:00Z" - latency: 2.872304ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:00Z" - latency: 2.270336ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:00Z" - latency: 2.078946ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:30:00Z" - latency: 2.255513ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:29:00Z" - latency: 2.092872ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:28:00Z" - latency: 2.169527ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:27:00Z" - latency: 2.569718ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:26:00Z" - latency: 2.25836ms message: 'network-check-target-ip-10-0-129-161: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:25:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-130-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "18427" uid: d64e5c5c-53fd-4c2b-ac1c-65ce3365a412 spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:27:00Z" message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.058µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 801.033µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:00Z" - latency: 875.113µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:00Z" - latency: 906.53µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:00Z" - latency: 993.389µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:30:00Z" - latency: 861.898µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:29:00Z" - latency: 752.516µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:28:00Z" - latency: 1.139709ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:27:00Z" - latency: 1.099017ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:26:00Z" - latency: 841.527µs message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:25:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-ip-10-0-131-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "18428" uid: 668d4cbd-f452-4505-94a1-f3a7917a09e8 spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T14:27:00Z" message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.695747ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 1.998924ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:33:00Z" - latency: 2.391076ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:32:00Z" - latency: 2.178355ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:31:00Z" - latency: 2.054584ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:30:00Z" - latency: 1.955134ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:29:00Z" - latency: 1.96195ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:28:00Z" - latency: 1.967602ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:27:00Z" - latency: 2.481512ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:26:00Z" - latency: 2.38089ms message: 'network-check-target-ip-10-0-131-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:25:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T14:19:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-98-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-98.ec2.internal uid: bcefcf40-23ef-478d-a4d1-c08bb63f4ace resourceVersion: "20468" uid: 704d5417-1678-406f-8d76-a803d7119ff5 spec: sourcePod: network-check-source-8894fc9bd-4vkql targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T14:26:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.651µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:38:00Z" - latency: 1.736676ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:38:00Z" - latency: 911.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:37:00Z" - latency: 1.654371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:37:00Z" - latency: 891.488µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:36:00Z" - latency: 2.230845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:36:00Z" - latency: 878.285µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:35:00Z" - latency: 1.816129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:35:00Z" - latency: 1.101837ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T14:34:00Z" - latency: 1.882626ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T14:34:00Z" kind: List metadata: resourceVersion: ""