Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-10217

DBaaS: Delete VM operator upon unregister


    • Yes
    • 2
    • Yes
    • Yes
    • No
    • Server Integrations


      Special case after https://jira.percona.com/browse/PMM-9965
      If a user creates 2 clusters using the same Kubernetes config file, there will be 2 cluster names pointing to the same cluster.
      When you unregister one of them, the VM operator will be removed after https://jira.percona.com/browse/PMM-9965, resulting in a cluster that cannot be monitored.

      User impact:

      User deletes VM operator when unregistering a K8 cluster

      Steps to reproduce:

      Go to DBaaS and register k8s cluster
      Register a second cluster using the same Kubernetes config.

      Unregister one of them

      Actual result:

      VM operator is removed from the cluster that still exists.

      Expected result:

      VM operator remain installed.

      Proposed implementation

      Scenario: registering a new Kubernetes cluster
      When a new Kubernetes cluster is being registered
      Then the following labels should be added to the vm-operator's pod to identify it for operations like delete
        app.kubernetes.io/name: <cluster-name>
        app.kubernetes.io/part-of: pmm
        app.kubernetes.io/managed-by: ?????
        app.kubernetes.io/created-by: pmm?
      Scenario: unregistering a Kubernetes cluster
      When a new Kubernetes cluster is being unregistered
      Then Remove the vm-operator where the label app.kubernetes.io/name matches the cluster name


        Issue Links



              Unassigned Unassigned
              carlos.salguero Carlos Salguero
              0 Vote for this issue
              1 Start watching this issue



                Smart Checklist