Skip to main content
Crossplane providers continuously reconcile desired state by calling cloud APIs. Compatibility depends on the provider family, provider version, managed resource, endpoint configuration, and every operation used by reconciliation and deletion. Do not begin with a Composition. First prove one managed resource in an isolated control plane.

​
Start a local adapter

Start one service mapping before testing a composition. The bounded example uses S3 backed by Google Cloud Storage:
1

Install or update the Tensor9 CLI

Install the customer CLI with Homebrew, then confirm the binary is available:
If tensor9 is already installed, run brew upgrade tensor9 instead of the install command.
2

Authenticate with Tensor9

A Tensor9 API key is required. Use the key issued during onboarding, or email [email protected] to request one for your organization. Do not share your account or key with another customer or organization.If your secret manager has already supplied T9_API_KEY, skip the prompt. Otherwise, enter your key at a hidden prompt in the terminal where you will run tensor9:
Check that the variable is set without printing it, then verify your Tensor9 identity:
Confirm that the reported identity belongs to the intended customer account. Do not continue if authentication fails or the account is wrong. Keep shell tracing disabled while using the key. Do not paste the key into commands, shell profiles, source files, screenshots or support messages.See Install and Authenticate for the planned license lifecycle, entitlements and credential boundaries.
3

Inspect the S3 to Google Cloud Storage mapping

Ask Tensor9 to describe the exact directed service mapping used by this guide:
Read the supported S3 operations and Google Cloud Storage limitations before starting the process. The mapping is directional: this command describes S3 requests adapted to Google Cloud Storage, not the reverse direction.
4

Prepare Google Cloud access

Authenticate with Google Cloud using its standard Application Default Credentials chain. The adapter uses that identity when it calls Google Cloud Storage.Use a dedicated test project and narrowly scoped credentials. Do not put credentials in the command line, source code, or screenshots.
5

Start the S3 service adapter

Run the S3 to Google Cloud Storage adapter as a foreground process:
Leave this terminal open. This is the current foreground launcher, not the pending Docker launcher for local development mode. It calls your actual target-cloud services; it is separate from the in-memory emulator. Acquisition and license renewal require Tensor9 authentication. Keep the endpoint local to your test.
6

Copy the listening endpoint

When the command reports its listening endpoint, copy that exact value into a second terminal:
Keep the endpoint local to the test unless you have deliberately configured network access and authentication for another machine.
7

Run one bounded S3 request

Continue with this page’s client or tool instructions. Point only S3 at T9_CLOUD_ADAPTER_ENDPOINT, then perform one operation whose Google Cloud Storage effect you can verify independently.Check both sides: read the S3-shaped response and inspect the native object or bucket in Google Cloud Storage. A successful client response alone does not prove that the target state is correct.
8

Stop the local adapter

Return to the first terminal and press Control-C. Confirm the process exits before deleting the test object or bucket with Google Cloud’s native client.If the request failed, preserve the request ID, adapter endpoint, S3 operation name, Google Cloud request ID, and any x-t9-explain-* receipt headers before stopping the process.

​
Choose and pin the provider

Record:
  • the provider package and version;
  • the managed resource kind and API version;
  • the controller image digest;
  • how that provider version configures a custom endpoint;
  • which origin identity the controller uses;
  • the deletion policy and target resource owner.
Endpoint fields differ between provider families and versions. Use the provider’s published schema for the installed version rather than copying a ProviderConfig from another family.

​
Start with one bounded resource

Choose a resource with a small lifecycle, such as one object or bucket only when its full create, observe, update, and delete operations are documented for the selected target. Give it a unique external name and no production dependencies. Apply the provider configuration and one managed resource, then observe:
Record the Ready and Synced conditions, reason, message, observed generation, external name, and controller request identifiers. A healthy provider pod does not prove the managed resource reconciled.

​
Verify the reconcile loop

Test each phase separately:
  1. Observe absent: controller confirms the target resource does not exist.
  2. Create: controller issues the documented create operation.
  3. Observe present: controller reads back identity and late-initialized fields.
  4. No-op reconcile: a second pass does not mutate the target.
  5. Update: change one supported mutable field and observe convergence.
  6. Drift: make one controlled target-side change and observe correction or reporting.
  7. Delete: remove the managed resource and verify the configured deletion policy.
Inspect native target state after every mutation. Reconciliation retries can repeat uncertain writes, so test operation idempotency and bound controller concurrency before using shared resources.

​
Composition comes later

A Composition introduces multiple managed resources, dependency ordering, patches, readiness checks, connection details, and rollback questions. Add it only after every underlying resource has its own passing lifecycle fixture and cleanup evidence.

​
Common failure boundaries

Compare the exact operations with the service catalog and use diagnostic response headers where the provider exposes them.