New Default Crossplane Registry in Crossplane 1.15
Crossplane changes the default registry from DockerHub to xpkg.upbound.io in the Crossplane v1.15.0 release.| The Crossplane Blog
Providers enable Crossplane to provision infrastructure on an external service. Providers create new Kubernetes APIs and map them to external APIs. Providers are responsible for all aspects of …| Crossplane Documentation
This page shows how to install a custom resource into the Kubernetes API by creating a CustomResourceDefinition. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgro...| Kubernetes
Crossplane installs into an existing Kubernetes cluster, creating the Crossplane pod, enabling the installation of Crossplane Provider resources. Tip If you don’t have a Kubernetes cluster …| Crossplane Documentation
Crossplane changes the default registry from DockerHub to xpkg.upbound.io in the Crossplane v1.15.0 release.| The Crossplane Blog
Crossplane and Upbound warmly welcome Brian Lindblom from Apple and Bob Haddleton from Nokia to the Crossplane Steering Committee.| The Crossplane Blog
