Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Penyimpanan objek
Object Storage API mencakup bagian Kubernetes Resource Model (KRM) dan S3 REST API. Block storage dikelola dengan API penyimpanan Kubernetes standar (https://kubernetes.io/docs/concepts/storage/).
Object Storage API menggunakan resource kustom Kubernetes dan mengandalkan Model Resource Kubernetes. API ini digunakan untuk penyediaan dan administrasi resource penyimpanan objek. Kebijakan ini digunakan untuk mengelola siklus proses resource penyimpanan objek dalam organisasi, termasuk membuat, membaca, memperbarui, dan menghapus bucket. API juga digunakan untuk mencantumkan, menetapkan kebijakan retensi, dan menetapkan kelas penyimpanan bucket dan kontrol akses tingkat bucket.
Endpoint layanan dan dokumen penemuan
URL berikut adalah endpoint API untuk Object Storage API:
https://MANAGEMENT_API_SERVER_ENDPOINT/apis/object.gdc.goog/v1 dengan MANAGEMENT_API_SERVER_ENDPOINT adalah endpoint API server Management API Anda.
Dengan menggunakan perintah kubectl proxy, Anda dapat mengakses URL tersebut di browser atau
dengan alat seperti curl untuk mendapatkan dokumen penemuan untuk Object Storage
API. Perintah kubectl proxy membuka proxy ke server Kubernetes API di komputer lokal Anda. Setelah perintah tersebut berjalan, akses dokumen di
URL berikut: http://127.0.0.1:8001/apis/object.gdc.goog/v1.
Ringkasan S3 REST API
Software-defined storage
menyediakan Object Storage API yang kompatibel dengan Amazon S3 API. Google Distributed Cloud (GDC) air-gapped appliance Object Storage XML API adalah antarmuka RESTful yang memungkinkan Anda mengelola data penyimpanan objek secara terprogram. Sebagai RESTful API, API ini mengandalkan informasi metode dan informasi cakupan untuk menentukan operasi yang akan dilakukan:
Informasi metode. Anda menentukan informasi metode dengan metode HTTP standar, seperti DELETE, GET, HEAD, dan PUT.
Informasi cakupan. Anda menentukan informasi cakupan dengan endpoint (URI) yang dapat diakses dan berbagai parameter cakupan. Untuk XML API, parameter cakupan utama adalah nama bucket dan objek. Cakupan operasi Anda lebih lanjut dengan menggunakan header HTTP dan parameter string kueri.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThe Object Storage API, which includes KRM and S3 REST API sections, manages the lifecycle of object storage resources, using Kubernetes custom resources for provisioning and administration.\u003c/p\u003e\n"],["\u003cp\u003eThe API endpoint for Object Storage is located at \u003ccode\u003ehttps://ADMIN_CLUSTER_KUBERNETES_API_ENDPOINT/apis/object.gdc.goog/v1alpha1\u003c/code\u003e, which can be accessed through \u003ccode\u003ekubectl proxy\u003c/code\u003e to view the discovery document.\u003c/p\u003e\n"],["\u003cp\u003eThe S3 REST API enables programmatic management of object storage data, utilizing HTTP methods (DELETE, GET, HEAD, PUT) and scoping parameters like bucket and object names.\u003c/p\u003e\n"],["\u003cp\u003eBlock storage in GDC is managed through standard Kubernetes storage APIs and supports a single storage class, \u003cem\u003estandard-rwo\u003c/em\u003e, as demonstrated by the example persistent volume claim provided.\u003c/p\u003e\n"]]],[],null,["# Storage API overview\n\n| **Important:** To access the URLs on this page, you must connect to the internet. The URLs are provided for use when you have such access.\n\nObject storage\n--------------\n\nThe Object Storage API includes Kubernetes Resource Model (KRM) and S3 REST API sections. Block storage is managed with standard Kubernetes storage API (\u003chttps://kubernetes.io/docs/concepts/storage/\u003e).\n\nThe Object Storage API uses Kubernetes custom resources and relies on the Kubernetes Resource Model. The APIs are used for provisioning and administration of object storage resources. They are used to manage the lifecycle of object storage resources in the organization, including creating, reading, updating, and deleting buckets. The APIs are also used for listing, setting retention policies, and setting the storage class of buckets and bucket-level access control.\n\n### Service endpoint and discovery document\n\nThe following URL is the API endpoint for the Object Storage APIs:\n`https://`\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER_ENDPOINT\u003c/var\u003e`/apis/object.gdc.goog/v1` where \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER_ENDPOINT\u003c/var\u003e is the API endpoint of your Management API server.\n\nUsing the `kubectl proxy` command, you can access that URL in your browser or\nwith a tool such as `curl` to get the discovery document for the Object Storage\nAPI. The `kubectl proxy` command opens up a proxy to the Kubernetes API server\non your local machine. After that command is running, access the document at the\nfollowing URL: `http://127.0.0.1:8001/apis/object.gdc.goog/v1`.\n\n### S3 REST API overview\n\nSoftware-defined storage provides the Object Storage API compatible with the Amazon S3 API. The Google Distributed Cloud (GDC) air-gapped appliance Object Storage XML API is a RESTful interface that lets you to manage object storage data in a programmatic way. As a RESTful API, it relies on method information and scoping information to define the operations to perform:\n\n\u003cbr /\u003e\n\n- **Method information**. You specify the method information with standard HTTP methods, such as DELETE, GET, HEAD, and PUT.\n- **Scoping information**. You specify the scoping information with an accessible endpoint (URI) and various scoping parameters. For the XML API, the primary scoping parameters are the bucket and object names. Further scope your operations by using HTTP headers and query string parameters.\n\nBlock storage\n-------------\n\n### Volume storage API overview\n\nInteraction with storage within GDC occurs entirely using the Kubernetes storage primitives. To create persistent volumes, follow the documentation (\u003chttps://kubernetes.io/docs/concepts/storage/persistent-volumes/\u003e) by Kubernetes.\n\nHere is an example of a persistent volume claim: \n\n apiVersion: v1\n kind: PersistentVolumeClaim\n metadata:\n name: my_volume\n spec:\n accessModes:\n - ReadWriteOnce\n volumeMode: Filesystem\n resources:\n requests:\n storage: 1Gi\n storageClassName: standard-rwo"]]
