Skip to content

Update blog post to also mention applications #493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 11, 2024
Merged

Update blog post to also mention applications #493

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21b74ad
Update blog post to also mention applications
Nov 8, 2024
ffdb9b8
Update version ref to 0.9.9 for applications annotations fix
Nov 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions content/blog/2024-11-07-clustergroup-sequencing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Within the framework, we support resource hooks in three ways:
3. Exposing a new top-level clusterGroup object, extraObjects, that allows users full control of creating their own
resource hooks.

These features are available in version 0.9.8 and later of the Validated Patterns clustergroup chart.
These features are available in version 0.9.9 and later of the Validated Patterns clustergroup chart.

== Race Conditions: The Problem

Expand Down Expand Up @@ -81,11 +81,11 @@ apply resources in. The mechanism is described in the ArgoCD upstream docs https
resources in the numerically next sync-wave are synced. This mechanism gives us a way of having ArgocD help us enforce
order with objects that it manages.

== Solution 1: Sync-Waves for Subscriptions in clusterGroup
== Solution 1: Sync-Waves for Subscriptions (and/or Applications) in clusterGroup

The Validated Patterns framework now allows Kubernetes https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/[annotations] to be added directly to subscription objects in the clusterGroup. ArgoCD uses annotations
for Resource Hooks. The clustergoup chart now passes any annotations attached to subscriptions through to the
subscription object(s) that the clustergroup chart creates. For example:
The Validated Patterns framework now allows Kubernetes https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/[annotations] to be added directly to subscription objects and application objects in the clusterGroup.
ArgoCD uses annotations for Resource Hooks. The clustergoup chart now passes any annotations attached to subscriptions
through to the subscription object(s) that the clustergroup chart creates. For example:

[source,yaml]
----
Expand Down Expand Up @@ -150,6 +150,9 @@ In the case of this particular issue, it was not enough. But because all sequenc
sync-wave annotations, adding the annotation to the subscription object will be necessary for using the other
solutions.

The sequencing of applications would work the same way, with the same format for adding annotations to the application
stanzas in the clustergroup.

== Solution 2: The `sequenceJob` attribute for Subscriptions in clusterGroup

In this situation, we have a subscription that installs an operator, but it is not enough for just the subscriptions
Expand Down