apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "43899" uid: fcf933e8-55de-4fd5-94af-96c55f5f3abd spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:39:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.387846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 1.277522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 832.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 923.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:57:06Z" - latency: 1.066467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:06Z" - latency: 956.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:06Z" - latency: 1.00404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:06Z" - latency: 952.105µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:06Z" - latency: 939.43µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:06Z" - latency: 773.259µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "45379" uid: 4c808788-b105-4fa7-9fe6-459f2f30e13e spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:38:06Z" message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.721986ms message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:06Z" - latency: 9.052064ms message: 'load-balancer-api-external: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:02:06Z" - latency: 5.882545ms message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:06Z" - latency: 7.820921ms message: 'load-balancer-api-external: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:01:06Z" - latency: 5.338823ms message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 7.653595ms message: 'load-balancer-api-external: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:00:06Z" - latency: 4.444553ms message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 8.452158ms message: 'load-balancer-api-external: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:59:06Z" - latency: 3.875389ms message: 'load-balancer-api-external: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 9.49809ms message: 'load-balancer-api-external: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:58:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "45378" uid: ae5b85e4-b6a0-4429-92c8-e148ab058835 spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:38:06Z" message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.711808ms message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:06Z" - latency: 9.144797ms message: 'load-balancer-api-internal: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:02:06Z" - latency: 4.405118ms message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:06Z" - latency: 7.849391ms message: 'load-balancer-api-internal: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:01:06Z" - latency: 5.326065ms message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 7.709689ms message: 'load-balancer-api-internal: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T18:00:06Z" - latency: 4.437229ms message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 8.48219ms message: 'load-balancer-api-internal: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:59:06Z" - latency: 4.771397ms message: 'load-balancer-api-internal: tcp connection to a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 9.469991ms message: 'load-balancer-api-internal: resolved host name a995bbf1b2a844135aa0a80da29e8b28-211be44c789c746a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:58:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-network-check-target-ip-10-0-137-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "43896" uid: 5e7bf570-2d46-4eff-8adb-46b3c71259a3 spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:39:06Z" message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009789ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 913.813µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 872.807µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 846.897µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:57:06Z" - latency: 1.004675ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:06Z" - latency: 869.81µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:06Z" - latency: 788.517µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:06Z" - latency: 1.205126ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:06Z" - latency: 923.894µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:06Z" - latency: 935.528µs message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-network-check-target-ip-10-0-138-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "43897" uid: 83187b4e-3ce6-41d7-86a8-266ddf05b2b3 spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:39:06Z" message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.943531ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 2.333671ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 2.219533ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 2.118353ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:57:06Z" - latency: 2.314832ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:06Z" - latency: 2.265151ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:06Z" - latency: 2.402678ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:06Z" - latency: 2.083575ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:06Z" - latency: 2.066574ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:06Z" - latency: 2.392065ms message: 'network-check-target-ip-10-0-138-42: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-network-check-target-ip-10-0-139-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "43898" uid: 546f5657-0914-4cf1-9de1-7ba978ace317 spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:39:06Z" message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.953808ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 2.307658ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 2.589806ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 2.336422ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:57:06Z" - latency: 2.547753ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:56:06Z" - latency: 2.476373ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:55:06Z" - latency: 2.438087ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:54:06Z" - latency: 2.220174ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:53:06Z" - latency: 2.269853ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:52:06Z" - latency: 2.407527ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:32:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-109.ec2.internal uid: c5374785-0bdf-46c8-9029-473c0477e8e5 resourceVersion: "45377" uid: 008ab85c-ef6e-4985-bbad-2ca08db4288e spec: sourcePod: network-check-source-8894fc9bd-xpct5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:38:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 750.462µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:02:06Z" - latency: 1.749408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:02:06Z" - latency: 1.299074ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:01:06Z" - latency: 1.732177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:01:06Z" - latency: 833.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T18:00:06Z" - latency: 1.832153ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T18:00:06Z" - latency: 736.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:59:06Z" - latency: 1.771304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:59:06Z" - latency: 914.435µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:58:06Z" - latency: 1.811782ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:58:06Z" kind: List metadata: resourceVersion: ""