Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

EVEREST-496 Add multi-namespaces support to DBClusters #427

Merged

Conversation

recharte
Copy link
Collaborator

@recharte recharte commented Feb 6, 2024

EVEREST-496 Powered by Pull Request Badge

Add multi-namespaces support to DBClusters

NOTE FOR REVIEWERS: Still missing api-tests, I'll submit a follow-up PR to address the integration tests once the dependencies are sorted out.
Problem:
EVEREST-496

Add the namespace prefix to every DB related endpoint

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?

Tests

  • Is an Integration test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

With the introduction of VMAgent CR reconciliation in everest-operator
we no longer need to block the deletion of MonitoringConfigs if VMAgent
is using them.
With the introduction of VMAgent reconciliation in the everest-operator
we no longer need an endpoint to create its spec.
@recharte recharte requested a review from a user February 6, 2024 17:38
@recharte recharte changed the base branch from main to EVEREST-496-multi-namespaces-monitoring February 6, 2024 17:38
api/database_cluster_restore.go Outdated Show resolved Hide resolved
deploy/quickstart-k8s.yaml Outdated Show resolved Hide resolved
Base automatically changed from EVEREST-496-multi-namespaces-monitoring to EVEREST-495-multi-namespaces February 7, 2024 16:29
@recharte recharte merged commit 7d93a85 into EVEREST-495-multi-namespaces Feb 7, 2024
5 of 6 checks passed
@recharte recharte deleted the EVEREST-496-multi-namespaces-dbclusters branch February 7, 2024 16:41
@recharte recharte mentioned this pull request Feb 7, 2024
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants