Skip to content

Support namespaced resources in ExtraResources #483

@jtv8

Description

@jtv8

What problem are you facing?

The ExtraResources kind does not currently support namespace-scoped resources.

Now that Crossplane v2 is in public release and supports namespace-scoped managed resources, it's quite likely that users of this function will want to retrieve such a resource that already exists on the cluster and use its manifest in other resources.

In my specific case, I'd like to reference some of the parameters of a namespace-scoped ProviderConfig in another resource.

How could this Function help solve your problem?

Extend the ExtraResources API by allowing a namespace to be specified:

apiVersion: meta.gotemplating.fn.crossplane.io/v1alpha1
kind: ExtraResources
requirements:
  some-foo-by-name:
    # Resources can be requested either by name
    apiVersion: example.com/v1beta1
    kind: Foo
    matchName: "some-extra-foo"
    namespace: "some-namespace"

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions