-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Adding Details For an External MySQL DB Causes Deployment to Fail #10705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We should research this more. Try to replicated it. |
@mrsimonemms could you research this? |
I've tried this with the
My feeling is that, if you're moving databases then there's no easy path for extracting the data and ingesting into the external DB. The likely scenario is that this would be a POC where someone is investigating using the external DB. For that reason, whilst I think we should fix this issue, I don't think that it a super high priority. There is a fairly straightforward workaround to this - run |
Bug description
I was finally able to get an EKS cluster up and running. I ran the KOTS installation and that was fine and deployed without issue. I however forgot to setup the external database information, so I went back into the KOTS UI > Config. I unselected the 'Use In-Cluster MySQL' checkbox and filled out my database information. I clicked on 'Save config' and then deployed the new config after it passed it's checks. Almost immediately it showed me the deployment failed.
I am going to drop the error message in the self-hosted teams Slack channel.
Steps to reproduce
Of note, I haven't replicated this yet but that's what I did to get this issue.
Workspace affected
No response
Expected behavior
I would expect the new configuration to deploy without issue and the external MySQL database be used.
Example repository
No response
Anything else?
Error Message
The text was updated successfully, but these errors were encountered: