Generated banner for Open Knowledge Format for Crossplane v2
Generated logo for Open Knowledge Format for Crossplane v2

Open Knowledge Format for Crossplane v2

LLM wiki kit

First committed by jkroepke

Published in jkroepke/okf-crossplane-v2. Publisher page

37 GitHub stars

What it is

LLM-wiki in OKF (Open Knowledge Format) for Crossplane v2
— the description by jkroepke

AutoGineer overview, from the brain’s own files

The okf-crossplane-v2 repository provides a versioned, source-backed knowledge catalog designed to help AI agents and developers navigate the Crossplane v2 ecosystem. It aggregates information from Go API types, CRDs, package metadata, and documentation into a structured format. By utilizing the Open Knowledge Format (OKF), it enables agents to perform precise lookups on providers, composition functions, and API definitions. The project includes a dedicated MCP server that allows agents to query live repository data, such as CRD definitions, versioning, and examples, ensuring that the information retrieved is grounded in specific, versioned source code.

How it works

Memory model: LLM wiki

AutoGineer overview, from the brain’s own files

The system organizes technical knowledge into a catalog of Markdown files stored in the catalog folder. These files contain OKF metadata and provenance links. An MCP server, which can be self-hosted or used via a public endpoint, ingests this catalog into a DuckDB instance. Agents interact with this data through specific tools that resolve provider versions, search CRDs, and retrieve documentation or examples. The system relies on specialized researcher agents defined in the .agents folder to maintain and validate the knowledge base, ensuring that facts are linked to stable source code and documentation.

Folders
FolderRoleFiles
.codexagent-config25
.githubagent-config2
skillsagent-instructions1
.agentsfolder37
.codex-pluginfolder1
.okffolder2
.pifolder27
.pluginfolder1
catalogfolder120
mcpfolder12

Requirements

Apps: Docker

API keys (by name): GITHUB_TOKEN

Works with: Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Amp, Cline, JetBrains Junie, Devin (ex-Windsurf)

Set it up

  1. Download the brain as a ZIP and unzip it where you keep your notes or project: https://mp-staging.autogineer.com/agent-brains/jkroepke/okf-crossplane-v2/download
  2. Point Claude Code at .codex-plugin/plugin.json: it does not read that file on its own.

  3. cd okf-crossplane-v2 && claude

  4. AutoGineer scanned these files at commit df24ac2.

  5. Add crossplane-v2-okf to .mcp.json:

    {
      "mcpServers": {
        "crossplane-v2-okf": {
          "type": "http",
          "url": "https://crossplane.mcp.jkroepke.de/mcp"
        }
      }
    }
    
  6. Or add it with the Claude Code CLI:

    claude mcp add --transport http crossplane-v2-okf https://crossplane.mcp.jkroepke.de/mcp
  7. Your data is sent to crossplane.mcp.jkroepke.de.

  8. First committed by jkroepke. Published in jkroepke/okf-crossplane-v2. Licence: Apache License 2.0.

Usage

AutoGineer overview, from the brain’s own files

  • Querying CRD definitions for specific Crossplane providers
  • Retrieving versioned examples for composition functions
  • Resolving stable provider versions and their associated documentation
  • Integrating Crossplane knowledge into AI agent workflows via MCP
“Find the latest version of the AWS provider and list its CRDs.”
The agent uses the get_versions and provider_crd_search tools to return the canonical repository name and a list of available CRDs for the specified provider.
“Show me the definition for the S3Bucket CRD in the latest AWS provider.”
The agent retrieves the YAML definition of the requested CRD using the provider_crd_get_definition tool, ensuring the output is token-efficient.

Documentation by jkroepke

Image: CI Image: GitHub license Image: GitHub Repo stars Image: BundleDex

Open Knowledge Format for Crossplane v2

This repository provides a structured knowledge catalog for the Crossplane v2 ecosystem using Open Knowledge Format v0.2.

The goal is to make Crossplane concepts, APIs, providers, composition functions, documentation, and practical examples easier to discover and understand. The catalog is designed for both humans and knowledge-aware tools.

Installation

WARNING
The public MCP server is a temporary early-access service for early adopters. Its availability is not guaranteed, and it may change or be removed without notice. It is intended to bridge the current tooling gap until the OKF ecosystem provides practical, end-user-friendly solutions that run locally. For reliable or production use, self-host the included container.

Install the companion skill and hosted OKF-aware MCP server together as a plugin for every detected supported agent:

npx plugins add jkroepke/okf-crossplane-v2

Pass --target codex to install only in Codex. Restart the selected agents after installation.

Alternatively, install the hosted OKF-aware MCP server globally:

npx add-mcp \
  https://crossplane.mcp.jkroepke.de/mcp \
  --name crossplane-v2-okf \
  --global

Then install the companion skill so the agent prefers this bundle over generic documentation providers for Crossplane v2 questions:

npx skills add jkroepke/okf-crossplane-v2 \
  --skill crossplane-v2-okf \
  --global

Both standalone installers detect supported agents and ask where the integration should be installed. Restart the selected agent after installation.

The public MCP health endpoint is available at https://crossplane.mcp.jkroepke.de/healthz.

Self-hosting the MCP server

The included container fetches this repository, ingests catalog/ into a DuckDB catalog, and serves the okf-mcp tools over Streamable HTTP.

docker compose up --build --detach

To authenticate the server's GitHub requests, export GITHUB_TOKEN before starting the container. The token is optional.

The local MCP endpoint is http://127.0.0.1:8000/mcp. Put it behind a TLS reverse proxy for crossplane.mcp.jkroepke.de.

The catalog is refreshed at container startup. If fetching or ingestion fails and a previous catalog exists in the volume, the server continues with that last successful catalog.

The MCP tools are read-only, but the public endpoint has no application-level authentication. Apply request limits and access controls at the reverse proxy when required.

Crossplane package tools

The server adds these tools backed by OSS GitHub repositories:

  • get_versions(name) resolves an OSS provider or function repository and returns its canonical repository name, versions.latest, a compact list of recent stable versions, and tag counts. Pass the returned provider name to the CRD tools.

  • provider_crd_search(provider_name, provider_version, crd_search_term) searches CRDs in one explicit provider package version. The search term supports case-insensitive shell-style wildcards.

  • provider_crd_get_definition(provider_name, provider_version, crd_name, path?) returns the complete CRD definition as token-efficient YAML. Use a dotted path such as .spec or .spec.versions[0] to return only a subtree.

  • provider_crd_get_examples(provider_name, provider_version, crd_name) returns GitHub repository paths for generated and handwritten examples. Without an API version, it selects the latest served CRD API version, for example examples-generated/namespaced/ec2/v1beta2/route.yaml.

  • provider_crd_get_terraform_docs(provider_name, provider_version, crd_name) returns the Terraform provider repository, version, and documentation path. It reads the Crossplane provider Makefile and the generated controller mapping instead of inferring the Terraform resource name.

crd_name accepts a Kind, group/Kind, group/version/Kind, or a YAML fragment containing apiVersion and kind.

Use an OSS GitHub repository name such as crossplane-contrib/provider-upjet-aws or crossplane-contrib/function-go-templating. A small set of historical package aliases is mapped to their known OSS source repositories; unmapped upbound/... names are rejected rather than guessed.

The CRD tools require an explicit provider version. The value latest is also supported and selects the highest stable semantic-version Git tag. Self-hosted deployments need outbound HTTPS access to GITHUB_API_URL and GITHUB_RAW_URL.

Successful remote fetches are cached in memory. Git tag listings use the configurable short FETCH_CACHE_TTL_SECONDS (default: 300 seconds); CRDs, definitions, examples, and Terraform metadata resolved at immutable Git tags are cached for 30 days. FETCH_CACHE_MAX_ENTRIES (default: 512) bounds memory use.

Why this repository exists

Crossplane knowledge is distributed across many repositories and kinds of sources:

  • Go API types and runtime implementations

  • CustomResourceDefinitions and OpenAPI schemas

  • package metadata

  • tests and executable examples

  • official Crossplane documentation

  • community implementations and real-world composition examples

Upjet-based providers add another layer. Their Crossplane managed resources are generated from Terraform provider resources, while the Terraform documentation often contains more details about the underlying cloud APIs and configuration fields.

This repository connects these sources in one versioned catalog without replacing the original documentation.

Knowledge structure

Knowledge is stored as small Markdown documents under catalog/. Each document represents an independently useful concept and includes OKF metadata, provenance in sources, keyed claim footnotes, and relationships to related concepts.

Repository validation pins okf-ingest 0.11.0, which adds OKF v0.2 core support, including generated.at freshness fallback and preservation of the new frontmatter families (upstream support commit).

If the task is to build a Crossplane v2 Composition, start with the Composition developer route. It routes agents through separate API/provider, pipeline/security, and testing/packaging concepts without pretending that provider-specific schemas or credentials are universal.

The catalog is intended to be:

  • Source-backed: important statements link to source code, schemas, tests, examples, or official documentation.

  • Version-aware: sources are tied to specific repository revisions.

  • Navigable: overview documents connect related concepts without requiring readers to know the source repository layout.

  • Incremental: providers, functions, services, documentation areas, and example repositories can be added in focused batches.

License

This project is licensed under the Apache License 2.0.

catalog/functions/function-go-templating/extra-resources.md


type: function title: ExtraResources in function-go-templating description: Request cluster resources by name or labels and consume them directly or through pipeline context. resource: https://github.com/crossplane-contrib/function-go-templating/tree/0a1e6d386f4363fae257ddbfb5b497416370e830/example/extra-resources tags: [crossplane, composition-function, extra-resources, context] generated: { by: "process:okf-v0.2-migration", at: "2026-08-20T06:45:13Z" } sources:


Overview

A template can render the special meta.gotemplating.fn.crossplane.io/v1alpha1 ExtraResources object to ask Crossplane to fetch Kubernetes resources from the local cluster. Each entry under requirements has an arbitrary key that later identifies the returned group.[^readme-extraresources-declaration-dynamic-selectors-and-access][^requirement-fields-and-selector-conversion]

The implementation can return rendered selectors as response requirements and can consume matching resources when they are present in a function request. The bundled example emits a requirement and reads returned items in the same template.[^readme-extraresources-declaration-dynamic-selectors-and-access][^rendered-requirement-processing-and-response-requirements]

Schema

Each requirement supports:[^requirement-fields-and-selector-conversion]

FieldUseMeaning
apiVersionSemantically necessaryAPI version passed to the protocol selector. This function does not validate that it is non-empty.
kindSemantically necessaryKind passed to the protocol selector. This function does not validate that it is non-empty.
matchNameConditionalExact resource name. Used when it is non-empty.
matchLabelsConditionalLabel map. Used when matchName is empty; an empty map therefore selects by an empty label set.
namespaceNoNamespace for a namespaced resource. In v0.12.2 the implementation copies it only when matchName is non-empty; it is ignored on the matchLabels path. Omit it for a cluster-scoped resource.

The template itself may compute selector values from request data, including labels derived from the observed composite resource.[^readme-extraresources-declaration-dynamic-selectors-and-access]

Behavior

  • Multiple ExtraResources documents may contribute requirements, but requirement keys must be unique across the rendered output. A duplicate key produces a fatal function result.[^rendered-requirement-processing-and-response-requirements]

  • A non-empty matchName takes precedence over matchLabels. When matchName is empty, the function constructs a label selector from matchLabels.[^requirement-fields-and-selector-conversion] This conflicts with the field comment, which says defined labels cause the name to be ignored; the catalog follows runtime behavior.

  • The current required_resources protocol field receives every selector. For compatibility with the older interface, the deprecated extra_resources field also receives cluster-scoped selectors.[^rendered-requirement-processing-and-response-requirements]

  • Fetched results are exposed in template data by requirement key. getExtraResources . "key" reads the current request's requiredResources[key].items, falling back to extraResources[key].items; a missing key returns nil.[^direct-and-context-lookup-helpers]

  • The function copies fetched results into response context at apiextensions.crossplane.io/extra-resources. Within either the legacy extra_resources map or current required_resources map, request groups replace same-key groups from incoming context and unrelated context groups are retained.[^context-merge-behavior]

  • When both protocol maps are non-empty, the function processes legacy results first and current results second. Each merge starts from the incoming request context, so the second response-context write supersedes the first. Current required_resources groups therefore win; legacy-only groups from that same invocation are not guaranteed to survive.[^context-merge-behavior][^legacy-then-current-context-merge-call-order]

  • getExtraResourcesFromContext . "key" reads context[apiextensions.crossplane.io/extra-resources][key].items; a missing entry returns nil. This is useful in a later pipeline step or when reading resources accumulated by an earlier invocation.[^direct-and-context-lookup-helpers][^context-merge-behavior]

No-match execution

requiredResources is protocol terminology for resources Crossplane must try to fetch. It does not require at least one matching object. Crossplane v2.3.3 and function-go-templating v0.12.2 handle a successful zero-match lookup as follows:[^crossplane-protocol-contract-for-missing-required-resources][^crossplane-required-resource-fetch-repeat-and-stabilization-loop]

  1. The function returns the selector in its response requirements.

  2. Crossplane attempts the lookup and records the requirement key even when no object matched.

  3. Crossplane calls the function again with the empty result.

  4. The function renders normally. Once it returns the same requirements, Crossplane considers them stable and continues the Composition pipeline.

The released code preserves a low-level distinction between selector types:

SelectorZero-match representationOutcome
Exact matchNameKubernetes NotFound becomes a nil resource group without an error.The requirement key is recorded and the function is called again.
matchLabelsA successful empty List becomes a resource group with zero items.The requirement key is recorded and the function is called again.

The function helpers may expose a present zero-item path as an empty slice and an absent path as nil; protobuf-to-map conversion can also omit an empty repeated items field. Ordinary range treats both as zero elements, and the bundled examples normalize them with default (list).[^exact-name-notfound-and-label-list-fetch-behavior][^helper-tests-for-empty-items-and-absent-paths]

No-match behavior is therefore permissive by default: the composition continues and a range over the result emits nothing. A template that needs at least one object must enforce that condition itself. Template evaluation errors still produce a fatal function result, actual Kubernetes fetch errors other than NotFound abort the pipeline step, and requirements that keep changing eventually fail the bounded stabilization loop.[^crossplane-required-resource-fetch-repeat-and-stabilization-loop][^template-execution-fatal-result-path][^crossplane-fetch-error-propagation-into-the-composition-pipeline]

Example

This summarized pattern requests resources by label, then safely iterates over the returned list:[^readme-extraresources-declaration-dynamic-selectors-and-access][^bundled-direct-access-helper-example]

apiVersion: meta.gotemplating.fn.crossplane.io/v1alpha1
kind: ExtraResources
requirements:
  buckets:
    apiVersion: s3.aws.upbound.io/v1beta1
    kind: Bucket
    matchLabels:
      example: "true"
---
{{- range $resource := (getExtraResources . "buckets" | default (list)) }}
# Use $resource here.
{{- end }}

The example is summarized from the Apache-2.0-licensed project source; it is not a verbatim runnable Composition and the selected API version and kind must exist in the cluster.[^bundled-direct-access-helper-example][^repository-apache-2-0-license]

Template-side namespace filter

This illustrative template-side pattern retains the first returned item from the composite's namespace, then uses it outside the loop. break stops the template scan after that match:[^go-template-variable-assignment-scope-and-break][^variable-declaration-and-reassignment]

{{- $selected := dict }}
{{- $namespace := $.observed.composite.resource.metadata.namespace }}
{{- range $extraResource := (getExtraResources . "bucket" | default (list)) }}
  {{- if eq $extraResource.resource.metadata.namespace $namespace }}
    {{- $selected = $extraResource }}
    {{- break }}
  {{- end }}
{{- end }}

{{- if $selected }}
# Render a desired resource using $selected.resource here.
{{- end }}

getExtraResources reads the items already included in the function request; it does not construct or alter an ExtraResources selector.[^direct-and-context-lookup-helpers] This is therefore a template-side consumption filter: it can prevent cross-namespace items from influencing rendered desired resources, but cannot narrow the earlier all-namespace List, reduce its RBAC requirement, or avoid the associated lookup cost.[^requirement-fields-and-selector-conversion][^exact-name-notfound-and-label-list-fetch-behavior]

Sprig v3.3.0 has no predicate-based list filter or nested-field finder for this unstructured result shape. Its list helpers operate on whole list items, while pluck selects a top-level key from explicitly supplied dictionaries and dig traverses one dictionary. The range is therefore still needed to find a matching item; the variable assignment and break are Go-template syntax, not Sprig functions.[^go-template-variable-assignment-scope-and-break][^variable-declaration-and-reassignment][^sprig-list-helpers][^dictionary-helpers][^function-go-templating-s-sprig-function-map]

Limitations

  • The special ExtraResources object is a function rendering directive, not a Kubernetes object that is added to desired composed resources.[^rendered-requirement-processing-and-response-requirements]

  • Label selectors are equality maps only; this schema does not expose set-based selector expressions.[^requirement-fields-and-selector-conversion]

  • matchLabels works for cluster-scoped resources; the released tests cover both a non-empty label map and an empty label map.[^released-cluster-scoped-label-tests][^namespaced-exact-name-test] The limitation is namespace scoping: although the schema accepts namespace beside matchLabels, v0.12.2 returns the label selector before copying the namespace. Crossplane consequently receives an empty namespace and performs an all-namespace label list, subject to RBAC, rather than limiting the list to the supplied namespace. The only released namespaced test uses matchName.[^requirement-fields-and-selector-conversion][^exact-name-notfound-and-label-list-fetch-behavior][^released-cluster-scoped-label-tests][^namespaced-exact-name-test]

  • The README's response illustration shows arrays directly beneath requirement keys, but its access syntax and released helpers read an items envelope. Follow the implementation-backed requiredResources[key].items shape.[^readme-extraresources-declaration-dynamic-selectors-and-access][^direct-and-context-lookup-helpers]

  • Retrieval timing and any result-count limit are controlled by Crossplane's composition-function protocol, not by the template helper. The selected function source does not define its own count limit.

  • This function forwards empty apiVersion or kind strings and does not validate that exactly one match field is set. Any protocol-side rejection is outside the selected function source.[^requirement-fields-and-selector-conversion]

  • Because result lookup returns nil for absent paths, use default (list) before ranging when a request may have no result.[^direct-and-context-lookup-helpers][^bundled-direct-access-helper-example]

  • For a namespaced matchLabels requirement, a template-side namespace test filters only the returned results. It is not a retrieval-scope or least-privilege mitigation; use matchName when an exact name is available.

  • The early-stop pattern is first-match-wins. If multiple resources in the composite's namespace match, define a stronger selector or an explicit selection policy before using the retained item.

  • Do not use the word required as a cardinality guarantee. The selected protocol and implementations impose no minimum match count.[^crossplane-protocol-contract-for-missing-required-resources][^crossplane-required-resource-fetch-repeat-and-stabilization-loop]

Relationships

See template functions for all helper signatures and request data and context for the rest of the request available to templates. Composed-resource RBAC identifies the Crossplane Core service account as the required-resource read principal; do not grant these reads to the Function pod merely because the Function declared the selector.

[^readme-extraresources-declaration-dynamic-selectors-and-access]: README ExtraResources declaration, dynamic selectors, and access [^requirement-fields-and-selector-conversion]: Requirement fields and selector conversion [^rendered-requirement-processing-and-response-requirements]: Rendered requirement processing and response requirements [^direct-and-context-lookup-helpers]: Direct and context lookup helpers [^context-merge-behavior]: Context merge behavior [^bundled-direct-access-helper-example]: Bundled direct-access helper example [^repository-apache-2-0-license]: Repository Apache-2.0 license [^legacy-then-current-context-merge-call-order]: Legacy-then-current context merge call order [^crossplane-protocol-contract-for-missing-required-resources]: Crossplane protocol contract for missing required resources [^crossplane-required-resource-fetch-repeat-and-stabilization-loop]: Crossplane required-resource fetch, repeat, and stabilization loop [^exact-name-notfound-and-label-list-fetch-behavior]: Exact-name NotFound and label-list fetch behavior [^helper-tests-for-empty-items-and-absent-paths]: Helper tests for empty items and absent paths [^template-execution-fatal-result-path]: Template execution fatal-result path [^crossplane-fetch-error-propagation-into-the-composition-pipeline]: Crossplane fetch-error propagation into the Composition pipeline [^released-cluster-scoped-label-tests]: Released cluster-scoped label tests and namespaced exact-name test [^namespaced-exact-name-test]: namespaced exact-name test [^go-template-variable-assignment-scope-and-break]: Go-template variable assignment, scope, and break and variable declaration and reassignment [^variable-declaration-and-reassignment]: variable declaration and reassignment [^sprig-list-helpers]: Sprig list helpers and dictionary helpers [^dictionary-helpers]: dictionary helpers [^function-go-templating-s-sprig-function-map]: function-go-templating's Sprig function map

242 files

Advantages

  • Provides version-aware knowledge by linking facts to specific repository revisions. evidence: README.md
  • Connects distributed sources like Go APIs, CRDs, and documentation into a single navigable catalog. evidence: README.md

Limitations

  • The public MCP server is provided as an early-access service and is not intended for production use without self-hosting. evidence: README.md
  • Requires explicit provider versions for CRD tools, as it does not guess or infer versions automatically. evidence: README.md

Security

Risk level: Low risk

This brain runs

Agent instructions that run or fetch something (26)

  • .agents/agents/okf-function-go-templating-researcher/AGENT.md: Write for Crossplane users who want to install and use `function-go-templating` in Compositions.
  • .agents/agents/okf-reviewer/AGENT.md: `mise run lint` succeeds after the final fixes and before the root or parent agent creates a commit.
  • .agents/agents/okf-reviewer/AGENT.md: Run `mise run lint` as the final validation command.
  • .agents/skills/okf-open-knowledge-format/SKILL.md: If the user agrees to install:
  • .agents/skills/okf-open-knowledge-format/SKILL.md: uv tool install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: pip install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: kcmd push --dry-run
  • .agents/skills/okf-updates/SKILL.md: Run this workflow only after the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • .agents/skills/okf-updates/SKILL.md: Run at most three direct researchers at once.
  • .agents/skills/okf-updates/SKILL.md: A requester reply that selects one or more candidate IDs from this explicitly invoked workflow is explicit permission to run the normal OKF update logic for those candidates.
  • .agents/skills/okf-updates/SKILL.md: Run deterministic validation, `okf-reviewer`, and `mise run lint`.
  • .agents/skills/okf/SKILL.md: Run this workflow only after the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`.
  • .agents/skills/okf/SKILL.md: After all review fixes, run `mise run lint`.
  • .agents/skills/okf/SKILL.md: Commit every intended file only after reviewer approval and a successful lint run.
  • .agents/skills/okf/SKILL.md: Run the Core docs and Core code researchers together when a concept needs both user-facing guidance and exact served API shape.
  • .agents/skills/okf/SKILL.md: Run independent read-heavy research in parallel, with at most three direct agents.
  • .agents/skills/okf/SKILL.md: After all fixes, run `mise run lint` and fix every reported issue.
  • .agents/skills/okf/SKILL.md: The reviewer may return `APPROVED` only after the final lint run succeeds.
  • .agents/skills/okf/SKILL.md: Non-thinking coding models such as Qwen3-Coder-Next can run every project agent without incompatible reasoning controls.
  • .agents/skills/okf/SKILL.md: deterministic validation and `mise run lint` results
  • AGENTS.md: Run the normal workflow only when the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`, or selects a feature candidate returned by an explicitly invoked `$okf-updates`, `/skill:okf-updates`, or `/okf-updates` workflow.
  • AGENTS.md: Run update discovery only when the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • AGENTS.md: Run deterministic validation and the `okf-reviewer` before committing the changes.
  • AGENTS.md: After the final review fixes, run `mise run lint` before creating any commit.
  • AGENTS.md: After reviewer approval and a successful lint run, commit every intended change.
  • AGENTS.md: Create commits with a Developer Certificate of Origin sign-off by default by using `git commit --signoff` (or `git commit -s`).

MCP servers (1)

  • .mcp.json (crossplane-v2-okf): https://crossplane.mcp.jkroepke.de/mcp · uses the network
  • Low risk: network-instructions (.agents/skills/okf-open-knowledge-format/SKILL.md:214)

Attribution and licence

First committed by
GitHub avatar of jkroepkejkroepke
Publisher
Jan-Otto Kröpke (Community)
Source
jkroepke/okf-crossplane-v2 · commit df24ac2
Licence
Apache License 2.0 (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
jkroepke

AutoGineer is not affiliated with or endorsed by jkroepke.

Download

The ZIP holds the files AutoGineer serves, with ATTRIBUTION.md and the licence. Download okf-crossplane-v2.zip