apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "39880" uid: 2a9e92c2-7f92-4814-8911-326a3323f3ba spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 875.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:19Z" - latency: 1.156067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:19Z" - latency: 1.075574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:19Z" - latency: 752.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:19Z" - latency: 844.385µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:19Z" - latency: 789.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:19Z" - latency: 799.337µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:19Z" - latency: 904.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:19Z" - latency: 1.003339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:18:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "42096" uid: c574cb86-ff62-4864-9500-260d7a92867d spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.713519ms message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:31:19Z" - latency: 8.101195ms message: 'load-balancer-api-external: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:31:19Z" - latency: 3.729866ms message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:30:19Z" - latency: 7.076282ms message: 'load-balancer-api-external: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:30:19Z" - latency: 4.124511ms message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:29:19Z" - latency: 7.20075ms message: 'load-balancer-api-external: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:29:19Z" - latency: 4.583868ms message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:19Z" - latency: 8.511378ms message: 'load-balancer-api-external: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:28:19Z" - latency: 4.152704ms message: 'load-balancer-api-external: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 7.424927ms message: 'load-balancer-api-external: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "42095" uid: 7267a807-2a84-4e88-b2d8-629354b26d85 spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.071935ms message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:31:19Z" - latency: 8.059211ms message: 'load-balancer-api-internal: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:31:19Z" - latency: 3.91839ms message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:30:19Z" - latency: 7.045363ms message: 'load-balancer-api-internal: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:30:19Z" - latency: 4.110254ms message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:29:19Z" - latency: 7.26597ms message: 'load-balancer-api-internal: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:29:19Z" - latency: 4.628869ms message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:19Z" - latency: 8.479285ms message: 'load-balancer-api-internal: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:28:19Z" - latency: 5.019547ms message: 'load-balancer-api-internal: tcp connection to a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 7.369846ms message: 'load-balancer-api-internal: resolved host name a9e177b78605d42208f546cd23c02edf-3601b28e09d68436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:27:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-131-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "39878" uid: 13ef7a56-db55-420f-9f15-28ef43a401c1 spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:19Z" message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.255193ms message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 823.952µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:19Z" - latency: 814.993µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:19Z" - latency: 924.557µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:19Z" - latency: 687.916µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:19Z" - latency: 755.775µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:19Z" - latency: 836.792µs message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:19Z" - latency: 1.123133ms message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:19Z" - latency: 1.231487ms message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:19Z" - latency: 1.206265ms message: 'network-check-target-ip-10-0-131-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:18:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-137-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "39879" uid: 2f36cd24-9569-432a-ab4b-9e60ab5fef83 spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:19Z" message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.380103ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 2.140964ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:19Z" - latency: 2.270138ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:19Z" - latency: 2.189388ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:19Z" - latency: 2.059241ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:19Z" - latency: 2.227021ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:19Z" - latency: 2.175604ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:19Z" - latency: 1.990822ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:19Z" - latency: 2.190495ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:19Z" - latency: 2.302831ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:18:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-network-check-target-ip-10-0-139-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "39877" uid: 80b52683-d0bb-48bd-819a-31e1745dff03 spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:38:19Z" message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050965ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 2.023859ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:26:19Z" - latency: 2.101807ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:25:19Z" - latency: 2.073721ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:24:19Z" - latency: 2.159996ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:23:19Z" - latency: 2.520242ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:22:19Z" - latency: 2.032362ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:21:19Z" - latency: 2.247629ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:20:19Z" - latency: 1.781215ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:19:19Z" - latency: 2.400248ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:18:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-58.ec2.internal uid: 4ce05fb6-db6d-4149-983d-14fa142afc5a resourceVersion: "42094" uid: c73b3078-c2ae-41e1-a606-4eebe641f297 spec: sourcePod: network-check-source-8894fc9bd-4nlnm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:37:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.643µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:31:19Z" - latency: 1.484877ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:31:19Z" - latency: 787.146µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:30:19Z" - latency: 1.687631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:30:19Z" - latency: 825.627µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:29:19Z" - latency: 1.529139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:29:19Z" - latency: 962.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:28:19Z" - latency: 1.551891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:28:19Z" - latency: 833.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:27:19Z" - latency: 1.513147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:27:19Z" kind: List metadata: resourceVersion: ""