[Epic] Implement current "overlay" resources in the provider binary

[AaronFriel]

The following resources are implemented as "overlay" resources, hand-written in each of our supported languages. This has increased the cost of supporting these resources and ensuring they handle resource options such as dependsOn.

• Document dependsOn limitations for ComponentResource resources (Helm, YAML, Kustomize) #1773
• Helm v3 Chart does not convert input properties to output properties #1923
• Pass provider options to all invokes in component resources #1945
• [Python] MyPy Error on Output.all(ConfigFile().resources) #1729
• pulumi refresh targeting a yaml.ConfigFile or yaml.ConfigGroup should refresh all generated resources #1642
• Support dependsOn for YAML ConfigFile/ConfigGroup #1833
• & more

These resource types are currently only available as overlays:

• kubernetes:apiextensions.k8s.io:CustomResource
• kubernetes:kustomize:Directory
• kubernetes:yaml:ConfigFile
• kubernetes:yaml:ConfigGroup

And the Helm Chart resources have an upgrade path via Helm/v3 Release:

• kubernetes:helm.sh/v2:Chart
• kubernetes:helm.sh/v3:Chart

Tasks

Beta Give feedback

1. Decision on whether to create a component resource for kubernetes:helm.sh:v3/Chart or deprecate #2788
   kind/task resolution/fixed +2
   
2. [dotnet] codegen fix for resources without constant input properties pulumi#15488
   impact/no-changelog-required kind/bug language/dotnet +3
   
3. Support for non-overlay components in codegen for pulumi-kubernetes provider pulumi#15490
   area/codegen impact/no-changelog-required kind/enhancement language/dotnet +4
   
4. Develop Component resource for: kubernetes:yaml:ConfigGroup #2784
   3 of 3
   kind/enhancement resolution/fixed +2
   
5. Develop Component resource for: kubernetes:yaml:ConfigFile #2785
   2 of 2
   kind/enhancement resolution/fixed +2
   
6. yaml/v2: Detect file patterns automatically #2871
   area/yaml kind/bug resolution/fixed +3
   
7. Pulumi schema for resource references pulumi#15681
   area/component-packages kind/enhancement needs-triage resolution/duplicate +4
8. yaml/v2: apply the namespace uniformly to the resource name #2870
   area/yaml kind/bug resolution/fixed resolution/wont-fix +4
   
9. [yaml/v2] Improved resource prefix #2900
   impact/no-changelog-required +1
   
10. Update the codedoc examples for Yaml V2 components #2868
    area/yaml kind/task resolution/fixed +3
    
11. Develop Component resource for: kubernetes:helm:v4:Chart #2847
    3 of 20
    kind/enhancement +1
    
12. Develop Component resource for: kubernetes:kustomize:Directory #2786
    0 of 3
    kind/enhancement +1
13. Improve how we handle/surface errors in multi-language components pulumi#6933
    area/component-packages kind/enhancement size/M +3
14. Provider API docs show resources that aren't present in the SDK #2181
    area/docs kind/bug language/java mro2 +4
15. Develop Component resource for: kubernetes:apiextensions.k8s.io:CustomResource #2787
    0 of 2
    kind/enhancement +1
16. ConfigGroup (V2) resources aren't useable in Pulumi Go SDK #2910
    area/yaml blocked kind/bug +3
17. use "pulumi.json#/Resource" in yaml/v2 Resources #2918
    +0
    
18. Update the "pulumi new" template
19. Add new examples
20. Add an integration test

Resolves

Beta Give feedback

1. Support dependsOn for YAML ConfigFile/ConfigGroup #1833
   kind/enhancement mro1 resolution/fixed +3
   
2. Document dependsOn limitations for ComponentResource resources (Helm, YAML, Kustomize) #1773
   area/docs area/helm area/yaml kind/enhancement mro1 +5
3. Helm/YAML getResource and getResourceProperty options methods missing in Go, Python, C# #1174
   area/sdk kind/engineering mro1 +3
4. YAML/Helm getResource method fails silently on unknown resource name #1173
   area/sdk impact/usability kind/enhancement language/javascript mro2 +5
5. getResource not working without explicit default namespace #907
   area/sdk kind/bug language/javascript mro2 +4
6. Simplify YAML API (GetResource) with prompt values #1108
   area/yaml kind/enhancement mro2 +3
7. Attempting to deploy large CRDs hangs indefinitely with yaml.ConfigFile and kustomize.Directory #1960
   kind/bug mro2 resolution/duplicate +3
   
8. Kubernetes Resource Naming Convention Needs Rethinking #1689
   kind/question mro2 resolution/fixed +3
   
9. Pulumi considers objects different depending on what Platform (Windows/Linux) you use #1208
   kind/bug mro2 +2
   

[lblackstone]

master...lblackstone/mlc has a proof on concept for this work.

[geowalrus4gh]

Its really confusing. Document says CustomResource is supported by YAML runtime and even gave me an example.

Got this error

`      on Pulumi.yaml line 169:
     169:     type: kubernetes:apiextensions.k8s.io:CustomResource
    Error: error resolving type of resource resourceKarpenter: The resource type [kubernetes:apiextensions.k8s.io:CustomResource] is not supported in YAML at this time, see: https://github.com/pulumi/pulumi-kubernetes/issues/1971
      on Pulumi.yaml line 204:
     204:     type: kubernetes:apiextensions.k8s.io:CustomResource
`

[EronWright]

@geowalrus4gh sorry, the documentation is incorrect. Please subscribe to this issue: #2787

An easy workaround would be to use the ConfigGroup resource, for example:

name: issue-1971
runtime: yaml
description: A minimal Kubernetes Pulumi YAML program
resources:
  example:
    type: kubernetes:yaml/v2:ConfigGroup
    properties:
      objs:
      - apiVersion: karpenter.sh/v1beta1
        kind: NodePool
        metadata:
          name: the-pool