vfarcic/crossplane-kubernetes

Demo Manifests and Code Used in DevOps Toolkit Videos

Generate manifests

devbox shell

just package-generate

exit

Run Tests

devbox shell

just cluster-create

just test-watch

# Stop the watcher with `ctrl+c`

just cluster-destroy

exit

Publish To Upbound

devbox shell

# Replace `[...]` with the Upbound Cloud account
export UP_ACCOUNT=[...]

# Replace `[...]` with the Upbound Cloud token
export UP_TOKEN=[...]

# Replace `[...]` with the version of the package (e.g., `v0.5.0`)
export VERSION=[...]

just package-publish

exit

crossplane-kubernetes's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update providers to v1.13.0 (xpkg.upbound.io/upbound/provider-aws-ec2, xpkg.upbound.io/upbound/provider-aws-eks, xpkg.upbound.io/upbound/provider-aws-iam)

Detected dependencies

crossplane

providers/aws.yaml

• xpkg.upbound.io/upbound/provider-aws-eks v1.12.0
• xpkg.upbound.io/upbound/provider-aws-iam v1.12.0
• xpkg.upbound.io/upbound/provider-aws-ec2 v1.12.0

providers/azure.yaml

• xpkg.upbound.io/upbound/provider-azure-containerservice v1.5.0

providers/function-auto-ready.yaml

• xpkg.upbound.io/crossplane-contrib/function-auto-ready v0.2.1

providers/function-kcl.yaml

• xpkg.upbound.io/crossplane-contrib/function-kcl v0.9.4

providers/google.yaml

• xpkg.upbound.io/upbound/provider-gcp-container v1.8.0

providers/provider-helm-incluster.yaml

• xpkg.upbound.io/crossplane-contrib/provider-helm v0.19.0

providers/provider-kubernetes-incluster.yaml

• xpkg.upbound.io/crossplane-contrib/provider-kubernetes v0.14.1

github-actions

.github/workflows/build12.yaml

• actions/checkout v4
• jetpack-io/devbox-install-action v0.11.0

---

• Check this box to trigger a request for Renovate to run again on this repository

Removal of the Kubernetes provider

I am writing to seek clarification regarding a recent update involving the removal of the Kubernetes provider from the Crossplane-Kubernetes configuration. I have observed that, as a result of this change, certain aspects of resource creation, especially those defined in our Crossplane Resource Definition (XRD), have been impacted.

Specifically, I am interested in understanding the revised procedure for generating Kubernetes-related resources, such as namespaces, following the removal of the Kubernetes provider. Since these resources were previously managed through the Kubernetes provider, I would greatly appreciate your guidance on how we should now approach their creation and management.

[question] unused metadata PatchSet?

Hi @vfarcic, thanks for your great work in spreading k8s and gitops knowledge!

I was wondering why there's a PatchSet named metadata in all your compositions, but it is never used/called in the actual patch (even more so now that you switched to functions).

From what I can read in the documentation, PatchSets would only be applied to resources that include them using type: PatchSet and name: metadata in the patches, but there's no such thing anywhere in your compositions.

Am I reading the documentation wrong, or the metadata PatchSet is unused/useless?