-
Notifications
You must be signed in to change notification settings - Fork 5
DBAAS-972 Grant access to the newly created database instance in Atlas Operator #64
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
base: dbaas-refactor-rebased
Are you sure you want to change the base?
DBAAS-972 Grant access to the newly created database instance in Atlas Operator #64
Conversation
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
…/namespaces for the same Atlas cluster
…et has been deleted or credentials are expired
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
Signed-off-by: Tommy Hughes <[email protected]>
…or DBaaSConnection
…ssue when no atlas project CR is found
Signed-off-by: Tommy Hughes <[email protected]>
Fix code issues after rebasing on 8/31
…processing connections
…processing connections: add unit test
DBAAS-956 MongoDB Atlas Operator incorrectly sets host to empty when processing connections
… on Thanos loaded on Grafana with status True (RHEcosystemAppEng#62) * DBAAS-906 Operator Metrics - Instance with Pending status on Thanos loaded on Grafana with status True * DBAAS-906 Operator Metrics - Instance with Pending status on Thanos loaded on Grafana with status True: address review comments * DBAAS-906 Operator Metrics - Instance with Pending status on Thanos loaded on Grafana with status True: address review comments
4da02c0
to
f8629f7
Compare
// GetPublicIP returns the static outbound public IP of the OpenShift Cluster | ||
// Or when the operator runs locally, the h | ||
func GetPublicIP() (string, error) { | ||
req, err := http.Get("http://ip-api.com/json/") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://ip-api.com/ says "Free for non-commercial use, no API key required"... which is fine as an open source project. Gets tricky when deploying to managed environments or as an official RH product. We need to discuss this a bit more i think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tchughesiv as we discussed earlier, we won't set the default to use the current cluster public IP as the IP may change, or may have multiple IPs (for AWS). Instead, we ask the user to provide the IP. In addition, the code is updated to make sure that when a new db instance is created for an existing Atlas Project, the project's IP access list remains the same in Atlas. The unit test has also been updated accordingly.
cc41886
to
3903485
Compare
52df71c
to
ce506a8
Compare
Currently, after a MongoDB instance is created with a new Atlas Project, the user has to go to the Atlas Portal to add the ip address to the ip access-list before an application can connect to the newly created db instance.
This enhancement is for the Atlas Operator to automatically grant access to the newly created database instance so that the above manual step can be avoided.
Tested successfully in a local devt cluster.