PromotionRequest expresses the intent to promote a piece of Freight to a specific set of Targets. Its Stage and Freight are fixed for its lifetime, giving it a single freight transition to represent from start to terminal state; only its list of Targets may change, so that Targets discovered after creation can still be included.
Unchanged since Kargo v1.12.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Spec describes the Stage, the Freight, and the Targets of the PromotionRequest.
Freight specifies the piece of Freight promoted by the Stage. The Freight MUST be in the same namespace as the PromotionRequest.
Stage specifies the name of the Stage that promotes the Freight. The Stage MUST be in the same namespace as the PromotionRequest.
Targets names the Targets to which this PromotionRequest promotes Freight. Each Target MUST be in the same namespace as the PromotionRequest. The list may be empty, which records that the governing Stage governed no Targets when the PromotionRequest was created -- distinct from the field being absent, which asks for it to be resolved. This is a resolved list, not a selector: the Stage's target selectors are evaluated once, at creation, and the result recorded here. The membership of the PromotionRequest is therefore a snapshot of what the Stage governed at that moment, and its threshold and terminal state are computed against it rather than against a selector that could match differently later. This is the only mutable field in the spec. The governing Stage owns it, and may add Targets to an in-flight PromotionRequest so that Targets discovered after creation can still receive the Freight. Target names MUST be unique; this is enforced by the validating webhook rather than by the schema, since a list-map's per-item ownership tracking would roughly double the storage cost of every entry.
Name is the name of the Target.
Status describes the per-Target progress and the aggregate state of the PromotionRequest's Promotions.
Conditions contains the last observations of the PromotionRequest's current state.
lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.
message is a human readable message indicating details about the transition. This may be an empty string.
observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.
reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.
status of the condition, one of True, False, Unknown.
type of condition in CamelCase or in foo.example.com/CamelCase.
FinishedAt is the time at which the PromotionRequest completed.
Message is a display message explaining the current Phase: what the PromotionRequest is waiting on, how far its fan-out has progressed, or why it did not succeed. i.e. If the Phase field has a value of Failed or Errored, this field can be expected to explain why.
ObservedGeneration is the generation of the spec last reconciled.
Phase is a high-level summary of the PromotionRequest's lifecycle.
StartedAt is the time at which the PromotionRequest started.
Summary aggregates the phases of this PromotionRequest's child Promotions.
Aborted is the number of child Promotions in the Aborted phase.
Errored is the number of child Promotions in the Errored phase.
Failed is the number of child Promotions in the Failed phase.
Pending is the number of child Promotions in the Pending phase.
Running is the number of child Promotions in the Running phase.
Succeeded is the number of child Promotions in the Succeeded phase.
Targets records progress against spec.targets: one entry per Target, with the child Promotion promoting to it and that Promotion's phase. Entries appear as the reconciler acts on each Target in spec.targets. The list is atomic rather than a map keyed by name: the reconciler is its only writer, so per-item ownership tracking in managedFields would only inflate the object -- roughly doubling the storage cost of each entry -- without ever being used to merge.
Name is the name of the Target.
Phase is the phase of that Promotion.
Promotion is the name of the child Promotion currently promoting the Freight to this Target. Empty if none has been created yet.
Source: kargo.akuity.io_promotionrequests.yaml
Changes to PromotionRequest (kargo.akuity.io/v1alpha1) in each Kargo version, compared to the version before it.
PromotionRequest was first seen on this version of Kargo
Released · View PromotionRequest in v1.12.0
No examples of PromotionRequest yet. Contribute one on GitHub.
kubespec.dev