iiinova — where your digital self keeps evolving

The Crossplane community welcomes new contributors!

000

It’s a lot simpler in v2…

100

Crossplane v2 will let you use any kind of resource in compositions.

100

Managed resources are namespaced as well.

100

Composite resources in V2 are now namespaces.

100

Crossplane v2 first build is available. Goal is to make Crossplane more useful for more things.

100

Crossplane 1.20 is coming sometime in May.

100

Most recent release of Crossplane: v1.19

100

Provisioning a composition runs a pipeline of functions you can define.

100

How you define a custom resource definition to create a new API that extends off the Kubernetes API.

100

Example: platform engineer defines a Small PostgreSQL provisioning API…

100

Now standing room only in the Crossplane talk…

100

Composition of managed resources let you build your custom platform APIs

100

Managed resources are the basic building blocks for Crossplane compositions

100

Summary about what is a Crossplane…

100

Shout out for Crossplane v2.

000

They documented their journey in their engineering blog at this QR Code.

100

Showing how a GitOps pull request looks in their platform with output from their Bot of Bots workflow.

100

Their Bot of Bots that kicks off a workflow of Argo bots.

100

Their three key integration services running on Crossplane

100

How they integrated with their existing platform.

100

Key choices: Chose Crossplane to work with KRM Argo for CD Chose to integrate with existing use cases

100

Macquarie chose Crossplane to speed up service enablement and improve developer experience.

100

Why use Crossplane as the basis of your platform.

100

Crossplane provides functions in composition to allow you to dynamically define your desired state.

100

Crossplane allows bundling or composing cloud resources together to simplify and abstract them for end-users.

100

Crossplane uses Kubernetes to create a universal control plane.

100

They adopted Crossplane control planes to unify their multicloud experience.

100

Big bank with a multi-cloud strategy

100

Just need to abstract the abstraction 😂😂😂

100

This is related to building a platform without talking to your end users.

100

Your platform needs a Product Owner if you are treating your platform as a product.

100

Consider intensive feedback from one team at a time rather than broad surveys. Be actionable as opposed to just a data collector.

100

Surveys: crafting the right questions, but only give a limited point in time view. Instead: try to watch your users…

100

4 mistakes: 1. Relying on a mandate from leadership. 2. Lack of goals and metrics that support that goal 3. Building tools without talking to end-users 4.

100

Observability tooling is also a fundamental capability of platforms.

100

APIs are also a great control point for managing access.

100

API-building is important because they provide the basis for self-service and integration.

100

You aren’t in control if you use ready-made solution. Your business might outgrow these.

100

You are doomed without buy-in from leadership.

000

Centralizing ops without providing self-service is doom #2.

000

You’re doomed if you think of your platform as a portal…

100