Skip to content

S3 buckets: console walkthrough

The same operations as the step-by-step guide, done in the console.

This console page has a guided tour

Click Start the tour beside the create button for a walkthrough that highlights each field as you go.

List

WebHosting > Storage > S3 lists the bucket claims in the selected project.

The Phase column is the one to read. Bound means the bucket exists and the credentials have been written into your project. Anything else means the claim has not completed.

Create

Create Bucket opens a guided form.

  • Name - names the claim, and with it the ConfigMap and Secret your application will read. It is not the name of the bucket itself.
  • Storage class - the backend. The list holds only bucket-capable storage classes, so anything shown here can serve a bucket. If the list is empty, none is installed on this cluster.
  • Bucket name - filled in for you as your project name followed by the claim name.

Keep the prefix on the bucket name

Bucket names are global to the storage backend, not scoped to your project. The project-name prefix is what stops your bucket colliding with another project's. Only change it if you have a reason, and keep a prefix that is yours.

A Summary appears once the form is complete. Read it before submitting - the storage class in particular cannot be changed afterwards.

Change

Nothing meaningful can be changed after a claim binds, and the console offers no edit form. The bucket name and the storage class are both fixed. See Change for what to do instead.

Delete

Use the kebab menu at the end of the row.

Deleting the claim usually deletes the bucket and its contents

The claim owns the bucket. Whether the data survives depends on the storage class's reclaim policy, and on this platform the object backends are set to delete it. Confirm before you delete - see Delete.

If a claim seems stuck deleting, wait rather than forcing it. The finalizer is what lets the operator release the bucket cleanly; removing it orphans the bucket on the backend.

Where the console differs from the CLI

Console oc
Bucket name Prefixed with the project for you You choose it, and own the collision risk
Storage class list Filtered to bucket-capable ones You check provisioner yourself
Reclaim policy Not shown Read it off the storage class before deleting
Credentials Written into the project either way Same ConfigMap and Secret