Skip to content

v0.0.4

Choose a tag to compare

@xtdong96 xtdong96 released this 30 Sep 20:48
4f3f6ad

Added

  • CCLClient.is_component_set_finished(*, name) reports whether a set is applied and
    reported converged, with one read. It requires successful validation and Application
    writes, completion conditions for the current generation, and a ComponentSet that is
    not being deleted.
  • CCLClient.get_component_set(*, name) and CCLClient.get_infraplane(*, name) read one
    object and return it as its model, raising NotFoundError if it does not exist.
  • component_set_current_conditions(component_set) returns the conditions the operator
    computed from the object's current generation, keyed by type, so a caller can read the
    reason and message behind a rollout that has not finished.
  • The operator and catalog Chart.yaml files carry home, sources and maintainers,
    and every cluster_base chart has a description. THIRD_PARTY_NOTICES.md records
    teleport-kube-agent as AGPL-3.0, fetched from upstream by Argo CD rather than
    redistributed.

Changed

  • Breaking: CCLClient(namespace, api_client=None) becomes
    CCLClient(namespace, *, api_client). api_client is required and there is no
    in-cluster default, so the caller decides which connection its clients share. Clients
    built on the same api_client reuse its API discovery results, so a client per
    namespace costs nothing more.
  • Breaking: Constructing a CCLClient reads and writes no object: it no longer
    creates its namespace. CCLClient.ensure_namespace() does, and is the only method that
    does, so a mistyped namespace fails against the API server rather than quietly gaining a
    working infra plane.
  • Breaking: CCLClient.create_infraplane and CCLClient.create_component_set are
    renamed apply_infraplane and apply_component_set. Both server-side apply, so they
    create the object or update it in place; the old names said only the first.
  • Breaking: CCLClient methods take the object's name by keyword only, for example
    delete_component_set(name="local-base").

Fixed

  • Application and AppProject reconciliation no longer deletes the Argo CD status and any
    pending operation on the objects it manages: the managed spec is replaced with a patch
    instead of a whole-object update. Explicit null Helm values survive a spec rewrite.
  • A CCLComponentSet waits for a referenced CCLInfraPlane whose status is still the
    previous generation's, rather than trusting an Available condition computed for an
    older spec. The status reports that separately from a plane that is not Available.
  • A write to an Application or AppProject built on a stale read is retried in place
    instead of failing the reconcile. Neither object has a status subresource, so Argo CD's
    own status writes move the resource version the operator's patch carries, and a read
    from the informer cache can miss an object that already exists. Neither lost race
    surfaces as a transient ApplicationFailed condition on the CCLComponentSet any more.
  • Pyright and Pylance no longer report apiVersion as a missing argument when a
    CCLInfraPlane or CCLComponentSet is constructed: CustomResource.api_version passes
    its default to Field by keyword, the only form type checkers read as a default.