Do not expose Admin endpoints and Admin Console with Quarkus

Hi everyone,
I am in the process of migrating from Keycloak 15 (Wildfly) to (Quarkus). I have solved most of the configuration problems encountered, also regarding the custom SPI.
However, I am currently at the security stage of the admin panel. In Wildfly distro - I implemented the solution that is described here: Admin endpoints and Admin Console and additionally appropriate redirections on the HTTP based on IP.
I can not find a similar solution in the Quarkus distro (v18). Is there something like that or only about the restrictions on the HTTP server?

For what it’s worth, potentially via the HTTP Apache IP rules. Blocked externally. Accessible from allowed IP address sets.