You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Tools like Kustomize have recognized the need to be provide a global ordering of resources created, as seen by kustomize supporting sortorder. This is used, for example, to ensure that a mutating admission webhook's dependencies are created before it is, which helps mitigate deadlocks and other deployment challenges.
With the upcoming release of yaml/v2.ConfigFile and yaml/v2.ConfigGroup and transformations unavailable, workarounds to apply CRDs and namespaces first are unavailable. One solution would be to add filtering, another would be to support a SortOrder.
This could dramatically simplify deploying complex manifests to a single resource, like this:
new k8s.kustomize.Directory(
`${name}-crds`,
{
directory: './kubeflow', // relative to Pulumi project root
sortOrder: [
// every subsequent entry has a DependsOn of all of the previous entries
{
group: [
{ kind: 'CustomResourceDefinition' },
{ kind: 'Namespace' },
],
},
{ kind: 'PodSecurityPolicy' },
// implicitly, all other resources:
]
},
{ ...opts, retainOnDelete: true },
);
Implementing this today is complex enough to require several resources and applies to manipulate dependsOn between them.
Hello!
Issue details
Tools like Kustomize have recognized the need to be provide a global ordering of resources created, as seen by kustomize supporting
sortorder
. This is used, for example, to ensure that a mutating admission webhook's dependencies are created before it is, which helps mitigate deadlocks and other deployment challenges.With the upcoming release of
yaml/v2.ConfigFile
andyaml/v2.ConfigGroup
and transformations unavailable, workarounds to apply CRDs and namespaces first are unavailable. One solution would be to add filtering, another would be to support aSortOrder
.This could dramatically simplify deploying complex manifests to a single resource, like this:
Implementing this today is complex enough to require several resources and applies to manipulate
dependsOn
between them.The text was updated successfully, but these errors were encountered: