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
We have enabled AWS private link for some of our kafka and postgres services. In the aiven console, we can view both the "dynamic" (regular) urls, and the private link urls.
When we create a ServiceUser, the generated secret contains only the dynamic/regular urls:
This makes it cumbersome for our dev teams to use the operator, as they need to use USENAME, PASSWORD and CA_CERT from the generated secret and configure the HOST elsewhere.
Would it be possible to get the operator to use the privatelink urls (if available) in the genererated secret?
We have enabled AWS private link for some of our kafka and postgres services. In the aiven console, we can view both the "dynamic" (regular) urls, and the private link urls.
When we create a
ServiceUser
, the generated secret contains only the dynamic/regular urls:This makes it cumbersome for our dev teams to use the operator, as they need to use
USENAME
,PASSWORD
andCA_CERT
from the generated secret and configure theHOST
elsewhere.Would it be possible to get the operator to use the privatelink urls (if available) in the genererated secret?
The text was updated successfully, but these errors were encountered: