In the microshift config.yaml.default file, the sidecar container named "logs" should be updated with "access-logs"

    4.20.0~0.nightly_2025_07_31_001616

    100%

1. get the node's name
% oc get nodes
NAME                         STATUS   ROLES                         AGE    VERSION
microshift-base-5639.local   Ready    control-plane,master,worker   4d3h   v1.33.2  
   
2. debug node to check config.yaml.default file
% oc debug node/microshift-base-5639.local
Starting pod/microshift-base-5639local-debug-lxbzh ...
To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
Pod IP: 10.1.235.165
If you don't see a command prompt, try pressing enter.
sh-5.1# chroot /host
sh-5.1# cd /etc/microshift/

3. In the config.yaml.default file, "logs" should be updated with "access-logs" for the name of the sidecar container 
 
            # The ingress operator configures the sidecar container named "logs" on
            # the ingress controller pod and configures the ingress controller to
            # write logs to the sidecar.  The logs are then available as container
            # logs.  The expectation is that the administrator configures a custom
            # logging solution that reads logs from this sidecar.  Note that using
            # container logs means that logs may be dropped if the rate of logs
            # exceeds the container runtime's or the custom logging solution's
            # capacity.

   "logs"

    "access-logs"