Skip to main content

How to disable celery-beat for a client

Disabling celery-beat for a client to remove the celery-beat component from Central Services.

Before you begin​

You need:

  • Access to the empower-tenant repository
  • VSCode to edit the YAML file(s).
  • The location of the configuration file: empower-tenant/tenants/empcentral-pd-aks/client/deploy.yaml.
  • Permission to create branch and submit pull requests.
  • Access to Weave GitOps (Prod)
warning

If you are missing any of these prerequisites, then you will not be able to complete the outlined steps

Procedure​

  1. After creating your branch, locate the deployment configuration file.

    empower-tenant/tenants/empcentral-pd-aks/<client>/deploy.yaml

  2. Change the required configuration keys under each organization.

    organizations:
       - name: augustus
         celeryBeatEnabled: false <-- set to false

  3. Save changes and submit PR and await approval.

  4. After your PR is approved, merge your PR.

  5. Verify the deployment

    Check the deployment status, application logs, health endpoint, or configuration-inspection command.

Verify the result​

Confirm that:

  • The deployment progresses as expected
  • The deployment reports a healthy state.
  • Celery-beat is removed from Central Services for the intended Client>Org>Env.
  • Scheduling and workflow triggers function as expected.

Post-Deployment Verification Steps​

Verify HelmReleases​

  1. Log into Weave GitOps

    https://gitops.empoweranalytics.io

  2. Go to Applications under the Delivery section:

    Weave Application

  3. Apply filters to narrow down the results to your target client

    1. Click the Filter icon
    2. enter empower-celery-beat-<client>-<env> into the search field¹
    3. Select HelmRelease under the Kind section
    4. Select the client's namespace
    5. Verify in the listed applications that the celery-beat HelmReleases are not present

    Weave Application Filtering

    ¹ Filtering Bug in Weave

    There is a known bug in the Weave Enterprise UI where the UI’s full-text filter has historically treated a dash (-) as a token separator or special character rather than preserving it as part of a literal name. Weave’s own release notes specifically call out that flux-system is interpreted as the two terms flux and system, rather than as an exact string.

    You MUST enter the name in its entirety for Weave to pull up the Application. Any combination of text and (-) will not work.

Verify Redis Dependencies​

The celery-beat component is a dependency to the redis-cache in Central Services. You can check the corresponding redis-cache dependencies to see if the celery-beat HelmRelease is present.

  1. Similar to the previous verifications step, under Applications filter for the client's redis-cache with "redis"

  2. Verify the empower-celery-beat-<client>-<env> is not tied to the redis-cache release.

    CB-Removed click on image to zoom

Common variations​

No variations available