The Kerberos infrastructure does not know what services are available to a particular user. Its job is to provide authentication information. It is then up to the service to determine whether that authenticated user is allowed to perform the requested operation.
That said, each service that wants to allow for Kerberos authentication needs to have a service principal setup in the/a KDC. The service may have a different realm then the realm for the user; however, a trust relationship will need to be set up between the relevant KDCs so that the service will be able to validate the service ticket provided by the user.
In a nutshell, once the user has as Kerberos ticket (via kinit), that user may request access to some service - typically using some client application. For example, curl, hdfs client, etc. The client application will use the user's Kerberos ticket and some service's principal name to request a service ticket from the KDC. The KDC will hand the client application the service ticket, which is then passed to the service. The service send the service ticket back to the KDC for validation. If valid, the service will trust the data and retrieve the user's principal from it. Sometimes the user's principal is used as-is or translated using configured auth-to-local rules into some local username. In either case, the service will somehow determine authorization. For example, using Ranger.