![]() ![]() ![]() The system confirms that the operation was successful. Then store the CLUSTER file in the root folder of the repo. By default it uses the GKE cluster set in kubeconfig context, you can specify the dedicated cluster (it must be set in the kubeconfig) in the file CLUSTER: GKECLUSTERgkemyclustercontextname. Create the ConfigMap by applying the YAML file. Using dedicated GKE cluster for manual charts testing. Set the KUBECONFIG environment variable to the path to the kubeconfig file for the Tanzu Kubernetes Grid management cluster. You can obtain vCPU capacity from a Tanzu Kubernetes Grid environment either manually or by running a Bash script. allkeys-lru first removes the less recently used (LRU) keys.Ĥ. Aggregate Total vCPU Capacity from a Tanzu Kubernetes Grid Installation. The maxmemory-policy directive defines the procedure to be applied when the memory limit is reached. The example configuration above sets the maxmemory directive and tells Redis to use the maximum of 2 MB of storage for the data set. Specify your Redis configuration in the data.redis-config section. Using a text editor, create a ConfigMap YAML that will store the Redis configuration.Ģ.The following steps explain how to configure Redis cache and a pod containing a Redis instance. Note: If you are using Minikube, you can simulate a two-node cluster by adding the -nodes option to the start command: minikube start -nodes 2 Deploying Redis on Kubernetes with ConfigMap
0 Comments
Leave a Reply. |