Menyiapkan MySQL sebagai layanan yang disediakan pengguna
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini memandu Anda mengikat Aplikasi ke instance MySQL yang tidak tercantum di marketplace Kf (termasuk Cloud SQL untuk MySQL) dengan Konektor Spring Cloud Foundry. Hal ini menyebabkan kredensial MySQL dimasukkan ke dalam Aplikasi, seperti mengikat ke layanan yang disediakan melalui paket marketplace.
Sebelum memulai
Pastikan Anda telah menginstal MySQL dan dapat diakses oleh cluster Kf.
Pastikan database untuk Aplikasi Anda telah dibuat.
Pastikan Anda telah menargetkan Ruang yang menjalankan Aplikasi Anda.
Membuat instance yang disediakan pengguna
Agar Kf berhasil mengikat Aplikasi ke instance MySQL Anda, variabel lingkungan minimum adalah URI (misalnya mysql://username:password@host:port/dbname). Pasangan nilai kunci tambahan dapat disertakan jika diinginkan. Dokumentasi MySQL dapat membantu saat membuat string URI.
Contoh berikut sudah cukup untuk deployment dasar:
Mulai ulang Aplikasi agar perubahan dapat diterapkan:
kfrestartapplication-name
Pastikan variabel lingkungan baru yang diberikan ke Aplikasi Anda:
kfvcap-servicesapplication-name
Memperbarui instance yang disediakan pengguna
Jika ada perubahan pada lingkungan (misalnya, pembaruan sandi atau host di
URI, atau penambahan key-value pair baru) yang perlu diteruskan ke
Aplikasi apa pun yang terikat dengannya, Anda dapat memperbarui instance yang disediakan pengguna:
[[["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."],[],[],null,["# Set up MySQL as a user-provided service\n\n| **Note:** You can leverage services that aren't listed in the marketplace by creating user-provided service instances that an App can bind to. Learn more about [user-provided services](../concepts/user-provided-services).\n\nThis document guides you through binding your App to a MySQL instance not listed in the Kf marketplace (including [Cloud SQL for MySQL](/sql)) with the Spring Cloud Foundry Connector. This results in the MySQL credentials being injected into the App, just like binding to services provisioned through marketplace plans.\n\nBefore you begin\n----------------\n\n- Ensure you have MySQL installed and accessible by your Kf cluster.\n- Ensure the database for your App has already been created.\n- Ensure you have targeted the Space running your App.\n\nCreate the user-provided instance\n---------------------------------\n\nFor Kf to successfully bind an App to your MySQL instance, the minimum environment variable is the URI (for example `mysql://username:password@host:port/dbname`). Additional key-value pairs may be included if desired. The [MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/connecting-using-uri-or-key-value-pairs.html) can help with creating a URI string.\n\nThe following example should be sufficient for basic deployments: \n\n kf cups \u003cvar translate=\"no\"\u003eservice-instance-name\u003c/var\u003e -p '{\"username\":\"\u003cvar translate=\"no\"\u003eusername\u003c/var\u003e\", \"password\":\"\u003cvar translate=\"no\"\u003epassword\u003c/var\u003e\", \"uri\":\"mysql://\u003cvar translate=\"no\"\u003eusername\u003c/var\u003e:\u003cvar translate=\"no\"\u003epassword\u003c/var\u003e@\u003cvar translate=\"no\"\u003emysql-host\u003c/var\u003e:\u003cvar translate=\"no\"\u003e3306\u003c/var\u003e/\u003cvar translate=\"no\"\u003edatabase\u003c/var\u003e\"}' -t \"mysql\"\n\nBind your App\n-------------\n\nNow that the user-provided service has been created, you can bind your App to\nthe instance name: \n\n kf bind-service \u003cvar translate=\"no\"\u003eapplication-name\u003c/var\u003e \u003cvar translate=\"no\"\u003eservice-instance-name\u003c/var\u003e\n\nRestart your App for the changes to take effect: \n\n kf restart \u003cvar translate=\"no\"\u003eapplication-name\u003c/var\u003e\n\nConfirm the new environment variables being provided to your App: \n\n kf vcap-services \u003cvar translate=\"no\"\u003eapplication-name\u003c/var\u003e\n\nUpdate the user-provided instance\n---------------------------------\n\nIf there are changes to the environment (for example password or host update in\nthe URI, or the addition of new key-value pairs) that need to be passed on to\nany App bound to it, you can update the user-provided instance: \n\n kf uups \u003cvar translate=\"no\"\u003eservice-instance-name\u003c/var\u003e -p '{\"uri\":\"\u003cvar translate=\"no\"\u003enew-uri\u003c/var\u003e\", \"\u003cvar translate=\"no\"\u003esome-new-key\u003c/var\u003e\": \"\u003cvar translate=\"no\"\u003esome-new-value\u003c/var\u003e\"}'\n\nWhat's next\n-----------\n\n- [VCAP_SERVICES](/migrate/kf/docs/2.7/how-to/app-runtime#vcapservices)\n- [Unbind service](../cli/kf-unbind-service)\n- [Delete service](../cli/kf-delete-service)"]]
