Description of problem:
After upgrade from 4.4 to 4.5 kibana indexes are not created and logs about the user shows this:

[2020-08-17T06:22:24,224][INFO ][c.a.o.s.p.PrivilegesEvaluator] [elasticsearch-cdm-g7ojzjry-2] No index-level perm match for User [name=Dirk.Egert, roles=[project_user], requestedTenant=__user__] Resolved [aliases=[.kibana_1687154965_dirkegert], indices=[], allIndices=[.kibana_1687154965_dirkegert_2], types=[doc], originalRequested=[.kibana_1687154965_dirkegert], remoteIndices=[]] [Action [indices:data/write/bulk[s]]] [RolesChecked [project_user]]
[2020-08-17T06:22:24,224][INFO ][c.a.o.s.p.PrivilegesEvaluator] [elasticsearch-cdm-g7ojzjry-2] No permissions for [indices:data/write/index, indices:data/write/bulk[s]]

i see that the index begin created/accessed is this one: 

.kibana_1687154965_dirkegert_2

i verified the roles extracting them with: 
$ oc exec <logging-es-POD> -- es_acl get --doc=roles

~~~
  "project_user": {
    "indices": {
...
      "?kibana_*_${user_name}": {
        "*": [
          "CRUD"
        ]
      }
    }, 
~~~

and find that this cannot match. I get a dump of the logging project and found that there is an alias created:

~~~
alias                        index                                                                 filter routing.index routing.search
.kibana_1687154965_dirkegert .kibana_1687154965_dirkegert_2                                        -      -             -
~~~

I would to verify if my analysis is correct. And if it is correct then look for answer to some questions:

1. Why this alias is created? is created as part of the upgrade? or was already there before?

2. how to resolve this situation? is it safe to just delete the alias?

I'm attaching privately the logs.

Thanks in advance