mirror of
				https://github.com/livebook-dev/livebook.git
				synced 2025-10-31 07:46:18 +08:00 
			
		
		
		
	
							parent
							
								
									8919a0eccd
								
							
						
					
					
						commit
						c22f3b7ac9
					
				
					 1 changed files with 7 additions and 2 deletions
				
			
		|  | @ -63,7 +63,7 @@ kind: Service | |||
| metadata: | ||||
|   name: livebook-loadbalancer | ||||
| spec: | ||||
|   type: LoadBalancer | ||||
|   type: ClusterIP | ||||
|   ports: | ||||
|     - port: 8080 | ||||
|       targetPort: 8080 | ||||
|  | @ -77,7 +77,10 @@ kind: Deployment | |||
| metadata: | ||||
|   name: livebook | ||||
| spec: | ||||
|   replicas: 3 | ||||
|   # When deploying Livebook for authoring notebooks to Kubernetes, | ||||
|   # the number of replicas must be 1, since Livebook considers you | ||||
|   # will assign one instance per user. | ||||
|   replicas: 1 | ||||
|   selector: | ||||
|     matchLabels: | ||||
|       app: livebook | ||||
|  | @ -134,6 +137,8 @@ data: | |||
|   LIVEBOOK_COOKIE: <base64_encoded_password> | ||||
| ``` | ||||
| 
 | ||||
| The setup above does not set up a data directory, which means once you restart the instance, any configuration will be lost. If you have a persistent volume, you can point the `LIVEBOOK_DATA_PATH` environment variable to it. | ||||
| 
 | ||||
| ## Deploy notebooks as applications | ||||
| 
 | ||||
| It is possible to deploy any notebook as an application in Livebook. Inside the notebook, open up the Application pane on the sidebar (with a rocket icon), click "Manual Docker deployment", and follow the required steps. | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue