Stepan Seliuk

Found thanks ;) ``` bash phuml -r ./ -graphviz -createAssociations true output.gv neato -Tpdf output.gv > output.pdf rm -f output.gv ```

Maybe it will be usefull: ``` php public static function updateAllUsingQuery( $attributes, Query $query, $params = [ ] ) { $params = array_merge( $params, $query->params ); if (is_null( $query->join ))...

I have the same, but I limited the agent at 12Gi and still I see this issue, OOMKilled. I tried to remove the limit and have seen 45Gi memory usage....

In the Kubernetic ingress I used these annotations: ``` annotations: nginx.ingress.kubernetes.io/auth-signin: 'https://$host/oauth2/start?rd=$escaped_request_uri' nginx.ingress.kubernetes.io/auth-url: 'https://$host/oauth2/auth' nginx.ingress.kubernetes.io/auth-response-headers: "x-auth-request-user, x-auth-request-groups, x-auth-request-email" ```

I confirmed with tcpdump and wireshark that Kubernetic receives these headers (populated): ``` x-auth-request-user: 11146279033.....\r\n x-auth-request-email: stepan@[REDACTED]\r\n x-auth-request-access-token: [REDACTED]\r\n ``` The user with the specified email I also added in...