apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "18703" uid: cdaca45e-12cc-4b47-b80e-1d2b7b469fb1 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T17:00:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:28Z" - latency: 1.169993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:28Z" - latency: 1.08321ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 858.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 1.135726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 1.093891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 894.799µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 907.774µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:28Z" - latency: 1.08761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:28Z" - latency: 1.260397ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "17714" uid: b19d8aed-e6ce-43f3-9af2-89f01f234ab5 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:59:28Z" message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.760943ms message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 6.961563ms message: 'load-balancer-api-external: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:05:28Z" - latency: 3.424147ms message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 6.794326ms message: 'load-balancer-api-external: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:04:28Z" - latency: 4.845707ms message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 6.865824ms message: 'load-balancer-api-external: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:03:28Z" - latency: 3.924082ms message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 6.293224ms message: 'load-balancer-api-external: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:02:28Z" - latency: 4.677579ms message: 'load-balancer-api-external: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 6.904983ms message: 'load-balancer-api-external: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "17715" uid: 7d12491e-5c69-462d-8f55-d4652c49c743 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:59:28Z" message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.807149ms message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 6.918792ms message: 'load-balancer-api-internal: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:05:28Z" - latency: 3.370646ms message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 6.824095ms message: 'load-balancer-api-internal: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:04:28Z" - latency: 5.05373ms message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 6.956823ms message: 'load-balancer-api-internal: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:03:28Z" - latency: 3.887507ms message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 6.274591ms message: 'load-balancer-api-internal: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:02:28Z" - latency: 3.786619ms message: 'load-balancer-api-internal: tcp connection to a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 6.929382ms message: 'load-balancer-api-internal: resolved host name a273a3ad6db5d4783919d01778f5d3e4-8ff54dae007d6ffe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-network-check-target-ip-10-0-128-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "18700" uid: 50522875-88b6-401a-9276-0f556f7e74a6 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:00:28Z" message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 825.427µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:28Z" - latency: 834.628µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:28Z" - latency: 826.185µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 1.148626ms message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 1.415344ms message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 878.616µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 727.984µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 795.761µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:28Z" - latency: 796.871µs message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:28Z" - latency: 1.128067ms message: 'network-check-target-ip-10-0-128-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-network-check-target-ip-10-0-130-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "18702" uid: eb4fb23b-5326-41ef-9a7f-d0c0efb9e78f spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:00:28Z" message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.175679ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:28Z" - latency: 2.065017ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:28Z" - latency: 2.036921ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 2.003291ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 2.000392ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 1.999426ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 1.605259ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 1.992109ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:28Z" - latency: 1.937145ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:28Z" - latency: 1.910633ms message: 'network-check-target-ip-10-0-130-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-network-check-target-ip-10-0-131-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "18701" uid: b366037e-952a-4b4f-89fb-4766adfe4922 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:00:28Z" message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.902318ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:28Z" - latency: 2.047749ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:28Z" - latency: 2.091822ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 1.859899ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 1.825123ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 1.935913ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 1.806971ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 1.933451ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:00:28Z" - latency: 1.794921ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:59:28Z" - latency: 1.88625ms message: 'network-check-target-ip-10-0-131-63: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:58:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:53:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-130-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-130.ec2.internal uid: 9dcc8981-5420-4938-9150-a27706bba43a resourceVersion: "17713" uid: f00e7366-7ff6-48ba-aad6-07e20058e9e7 spec: sourcePod: network-check-source-7b678d77c7-zr45l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:59:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.47µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:05:28Z" - latency: 1.681985ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:05:28Z" - latency: 1.062827ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:04:28Z" - latency: 1.597487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:04:28Z" - latency: 968.199µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:03:28Z" - latency: 1.580051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:03:28Z" - latency: 975.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:02:28Z" - latency: 1.767641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:02:28Z" - latency: 956.616µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:01:28Z" - latency: 1.947752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:01:28Z" kind: List metadata: resourceVersion: ""