apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50231" uid: d9528608-a239-47ba-92e2-aab9621bba13 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T18:26:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 737.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 724.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 1.407046ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 1.417583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 1.072137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 1.126179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:56:40Z" - latency: 1.071747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:55:40Z" - latency: 968.41µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:54:40Z" - latency: 1.049035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:40Z" - latency: 983.995µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50232" uid: 2b71c29c-5894-4976-a2b1-e7363c53d5b5 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:25:40Z" message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.892979ms message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 12.224396ms message: 'load-balancer-api-external: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:01:40Z" - latency: 3.829825ms message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 14.703404ms message: 'load-balancer-api-external: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:00:40Z" - latency: 4.453926ms message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 12.121947ms message: 'load-balancer-api-external: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:59:40Z" - latency: 4.157382ms message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 8.533657ms message: 'load-balancer-api-external: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:58:40Z" - latency: 4.537547ms message: 'load-balancer-api-external: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 8.138493ms message: 'load-balancer-api-external: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50233" uid: a6c2e196-a0a7-4647-99c6-e84729d2be66 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:25:40Z" message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.007204ms message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 12.24755ms message: 'load-balancer-api-internal: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:01:40Z" - latency: 3.57585ms message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 14.733136ms message: 'load-balancer-api-internal: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:00:40Z" - latency: 4.452777ms message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 11.958098ms message: 'load-balancer-api-internal: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:59:40Z" - latency: 4.128202ms message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 8.63307ms message: 'load-balancer-api-internal: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:58:40Z" - latency: 4.042945ms message: 'load-balancer-api-internal: tcp connection to a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 8.193114ms message: 'load-balancer-api-internal: resolved host name a4e4c76079b9b4a69820c334490841ef-1ded7e68b52d3dfc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-128-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50227" uid: ab2897e9-a887-4b38-9769-9a6f93ada425 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:26:40Z" message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 981.894µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 1.325177ms message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 1.683554ms message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 1.614799ms message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 772.017µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 849.579µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:56:40Z" - latency: 792.446µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:55:40Z" - latency: 788.685µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:54:40Z" - latency: 871.205µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:40Z" - latency: 933.656µs message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-130-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50228" uid: 879fd6d9-44b2-4e90-bfb8-f445432d575e spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:26:40Z" message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.092021ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 2.241394ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 2.22243ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 2.272145ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 2.274019ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 2.10516ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:56:40Z" - latency: 2.431523ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:55:40Z" - latency: 2.366478ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:54:40Z" - latency: 2.256411ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:40Z" - latency: 2.489906ms message: 'network-check-target-ip-10-0-130-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-138-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50229" uid: 0b1a85e8-f34e-4847-b20a-ed0269d11054 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:26:40Z" message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.747823ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 1.962338ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 2.052257ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 1.709481ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 2.077812ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 1.572255ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:56:40Z" - latency: 2.04627ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:55:40Z" - latency: 1.811078ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:54:40Z" - latency: 1.844357ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:53:40Z" - latency: 2.112164ms message: 'network-check-target-ip-10-0-138-194: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:52:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:19:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-205.ec2.internal uid: ef38967e-9d95-4a7a-bfa3-20850c14c1af resourceVersion: "50230" uid: 63eb09c1-3b56-4c82-8bf4-c2095fe702c0 spec: sourcePod: network-check-source-dbd9cf844-8ljvb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T18:25:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.911µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:01:40Z" - latency: 1.818062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:01:40Z" - latency: 839.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:00:40Z" - latency: 1.892122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:00:40Z" - latency: 896.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:59:40Z" - latency: 1.597424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:59:40Z" - latency: 894.117µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:58:40Z" - latency: 1.729829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:58:40Z" - latency: 727.76µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:57:40Z" - latency: 1.652256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:57:40Z" kind: List metadata: resourceVersion: ""