이 문서에서는 Spring Cloud Foundry Connector를 사용하여 Kf 마켓플레이스에 나와 있지 않은 Redis 인스턴스(Memorystore 포함)에 앱을 바인딩하는 방법을 설명합니다. 이렇게 하면 마켓플레이스 요금제를 통해 프로비저닝된 서비스에 바인딩과 같이 Redis 사용자 인증 정보가 앱에 삽입됩니다.
시작하기 전에
Kf 클러스터에서 Redis를 설치하고 액세스할 수 있는지 확인합니다.
Redis가 앱에 이미 설정되어 있는지 확인합니다.
앱을 실행하는 공간을 타겟팅했는지 확인합니다.
사용자 제공 인스턴스 만들기
Kf에서 앱을 Redis 인스턴스에 성공적으로 바인딩하는 경우 최소 환경 변수는 URI입니다(예: redis://:password@host:port). 원하는 경우 추가 키-값 쌍을 포함할 수 있습니다. 다음 예시는 기본 배포로 충분합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Set up Redis 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 Redis instance not listed in the Kf marketplace (including [Memorystore](/memorystore)) with the Spring Cloud Foundry Connector. This results in the Redis credentials being injected into your App, just like binding to services provisioned through marketplace plans.\n\nBefore you begin\n----------------\n\n- Ensure you have Redis installed and accessible by your Kf cluster.\n- Ensure Redis has already been set up for your App.\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 Redis instance, the minimum environment variable is the URI (for example `redis://:password@host:port`). Additional key-value pairs may be included if desired. The following examples should be sufficient for basic deployments.\n\n### For Redis with no AUTH configured\n\n kf cups \u003cvar translate=\"no\"\u003eservice-instance-name\u003c/var\u003e -p '{\"uri\":\"redis://\u003cvar translate=\"no\"\u003eredis-host\u003c/var\u003e:\u003cvar translate=\"no\"\u003e6379\u003c/var\u003e\"}' -t \"redis\"\n\n### For Redis with AUTH configured\n\n kf cups \u003cvar translate=\"no\"\u003eservice-instance-name\u003c/var\u003e -p '{\"uri\":\"redis://:\u003cvar translate=\"no\"\u003epassword\u003c/var\u003e@\u003cvar translate=\"no\"\u003eredis-host\u003c/var\u003e:\u003cvar translate=\"no\"\u003e6379\u003c/var\u003e\"}' -t \"redis\"\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.10/how-to/app-runtime#vcapservices)\n- [Unbind service](../cli/kf-unbind-service)\n- [Delete service](../cli/kf-delete-service)"]]