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
On an MSSQLDatabase, defining writeConnectionSecretToRef effectively does nothing, as no relevant information is contained in the secret that would be helpful in connecting to it. MSSQLServer does publish this information. However, in my case, the server is a shared resource, which may be used by many databases, which may be connected to by applications in different K8s namespaces. Having connection details only published from the server makes it impractical to replicate the secret to all the namespaces that require connection information.
What could help solve your problem?
Publish connection details to a MSSQLDatabase within the secret defined by writeConnectionSecretToRef. Useful fields would include the endpoint, username, and password.
The text was updated successfully, but these errors were encountered:
What problem are you facing?
On an
MSSQLDatabase
, definingwriteConnectionSecretToRef
effectively does nothing, as no relevant information is contained in the secret that would be helpful in connecting to it.MSSQLServer
does publish this information. However, in my case, the server is a shared resource, which may be used by many databases, which may be connected to by applications in different K8s namespaces. Having connection details only published from the server makes it impractical to replicate the secret to all the namespaces that require connection information.What could help solve your problem?
Publish connection details to a
MSSQLDatabase
within the secret defined bywriteConnectionSecretToRef
. Useful fields would include the endpoint, username, and password.The text was updated successfully, but these errors were encountered: