You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting with multiple clusters, a client file must be created for every user on every cluster - in case of 5 clusters and 100 developers that is 500 json files to manage.
This is mainly because client file contains connection details and connection key, which is very convenient for small installations.
For large installation can we separate connection details from key data? That is
use same user-specific key data across all clusters and
provide (or override) cluster connection details as late as during gefyra-con ?
Such separation would simplify work with large, multi installations.
Why would such a feature be important to you?
Reduce effort to manage multi-cluster installation with many users.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered:
What is the new feature about?
When interacting with multiple clusters, a client file must be created for every user on every cluster - in case of 5 clusters and 100 developers that is 500 json files to manage.
This is mainly because client file contains connection details and connection key, which is very convenient for small installations.
For large installation can we separate connection details from key data? That is
gefyra-con
?Such separation would simplify work with large, multi installations.
Why would such a feature be important to you?
Reduce effort to manage multi-cluster installation with many users.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: