Skip to content

adx-mon ManagementCommand does not report a completion condition #190

Description

@gossion

Problem

adx-mon creates adx.azure.com/v1alpha1 ManagementCommand resources to bootstrap the ADX control plane. In a deployed AKS environment, those resources can complete their intended work while status.conditions remains empty.

Terraform readiness logic that waits for a Ready or Succeeded condition on ManagementCommand therefore cannot determine completion and eventually times out. This was observed during an end-to-end TauGrid deployment validation.

The chart already documents this limitation in charts/taugrid-core/values.yaml: adx-mon does not currently provide a reliable ManagementCommand completion condition.

Why this matters

Consumers need a supported, machine-readable readiness signal before they can safely sequence dependent ADX resources. Without it, automation either blocks indefinitely or relies on timing assumptions.

Expected behavior

After a management command reaches a terminal outcome, adx-mon should expose a stable status contract, for example:

  • a condition with a documented type and terminal status;
  • an observed generation; and
  • failure details when the command cannot complete.

Acceptance criteria

  • Define and document the status contract for ManagementCommand completion.
  • Populate terminal success and failure conditions consistently.
  • Include enough diagnostic status for clients to report failures.
  • Add automated coverage for the contract.

Workaround

Do not gate Terraform deployment on ManagementCommand.status.conditions until this contract is available. ADX functions that depend on asynchronously created tables should use Kusto skipvalidation = 'true' where appropriate.

Upstream tracking

  • Azure/adx-mon#983 is an open upstream pull request that adds ManagementCommandExecuted and related terminal status conditions. It is the direct upstream fix for this missing status contract.
  • Azure/adx-mon#975 is a closed Function-status enhancement issue. Its related-work section explicitly identifies adding comparable conditions to ManagementCommand as follow-up work.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions