HowTo:CS Launch Terminal - Revision history

Carnold at 15:20, 29 November 2023

2023-11-29T15:20:15Z

← Older revision		Revision as of 11:20, 29 November 2023
Line 158:		Line 158:
	* '''Create your service''' using the following command:		* '''Create your service''' using the following command:
	** <code>kubectl apply -f test-adminer-service.yml</code>		** <code>kubectl apply -f test-adminer-service.yml</code>
	* You can now access this service from other pods in the same namespace, for example: <code>curl -V http://test-adminer-service:8080</code>		* You can now access this service from other pods in the same namespace, for example: <code>curl -v http://test-adminer-service:8080</code>

	== Create Ingress to Service ==		== Create Ingress to Service ==

2023-11-29T14:17:22Z

Create an Ingress to a Custom Application

← Older revision		Revision as of 10:17, 29 November 2023
Line 332:		Line 332:
	* '''Create your ingress''' using the following command:		* '''Create your ingress''' using the following command:
	** <code>kubectl apply -f test-chatbot-ingress.yml</code>		** <code>kubectl apply -f test-chatbot-ingress.yml</code>
			* Once created you should have a working URL to your web application.

2023-11-29T14:16:27Z

2023-11-29T13:44:53Z

← Older revision		Revision as of 09:44, 29 November 2023
Line 184:		Line 184:
	pathType: Prefix		pathType: Prefix
	</pre>		</pre>
			* '''Create your ingress''' using the following command:
			** <code>kubectl apply -f test-adminer-ingress.yml</code>
			* Once finished initializing, you should be able to access your deployment with the newly mapped URL.

2023-11-29T13:43:30Z

Create a Cluster Service

← Older revision		Revision as of 09:43, 29 November 2023
Line 158:		Line 158:
	* '''Create your service''' using the following command:		* '''Create your service''' using the following command:
	** <code>kubectl apply -f test-adminer-service.yml</code>		** <code>kubectl apply -f test-adminer-service.yml</code>
			* You can now access this service from other pods in the same namespace, for example: <code>curl -V http://test-adminer-service:8080</code>

			== Create Ingress to Service ==
			To expose your cluster service out to the Internet you create an ''Ingress'' that maps a public URL to your existing cluster service. This example is one just a basic map of an entire URL (path /). CS launch has a wildcard DNS entry for *.endeavour.cs.vt.edu so you can use any sub domain for your ingress that is not already in use. This example uses ''test-adminer.endeavour.cs.vt.edu''. CS launch uses nginx reverse proxy, there lots of ways to customize your ingress. See: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/
			* '''Log into your kubectl enabled terminal'''.
			* '''Create a new text file''' named <code>test-adminer-ingress.yml</code>. This file will describe your ingress as code.
			* Use the following code:
			<pre>
			apiVersion: networking.k8s.io/v1
			kind: Ingress
			metadata:
			name: test-adminer-ingress
			namespace: my-test-namespace
			spec:
			rules:
			- host: test-adminer.endeavour.cs.vt.edu
			http:
			paths:
			- backend:
			service:
			name: test-adminer-service
			port:
			number: 8080
			path: /
			pathType: Prefix
			</pre>

2023-11-29T13:31:23Z

Launch an App Using a Public Image

2023-11-29T13:29:15Z

Launch an App Using a Public Image

2023-11-29T13:15:40Z

Create a Cluster Service

← Older revision		Revision as of 09:15, 29 November 2023
Line 136:		Line 136:

	== Create a Cluster Service ==		== Create a Cluster Service ==
	Creating a ''ClusterIP'' service for your deployment will allow other pods in your namespace to be able to access your deployment through the cluster network. The name of your service will become the DNS name that other pods use to access, in this example: <code>test-adminer-service</code>. If you scale your deployment up, then the service will load balance network traffic to all of your pods.		Creating a ''ClusterIP'' service for your deployment will allow other pods in your namespace to be able to access your deployment through the cluster network. The name of your service will become the DNS name that other pods use to access, in this example: <code>test-adminer-service</code>. If you scale your deployment up, then the service will load balance network traffic to all of your pods. A cluster service is required to map an ingress to your deployment.
	* '''Log into your kubectl enabled terminal'''.		* '''Log into your kubectl enabled terminal'''.
	* '''Create a new text file''' named <code>test-adminer-service.yml</code>. This file will describe your service as code.		* '''Create a new text file''' named <code>test-adminer-service.yml</code>. This file will describe your service as code.

2023-11-29T13:13:06Z

← Older revision		Revision as of 09:13, 29 November 2023
Line 134:		Line 134:
	* '''Launch your app''' using the following command:		* '''Launch your app''' using the following command:
	** <code>kubectl apply -f test-adminer.yml</code>		** <code>kubectl apply -f test-adminer.yml</code>

			== Create a Cluster Service ==
			Creating a ''ClusterIP'' service for your deployment will allow other pods in your namespace to be able to access your deployment through the cluster network. The name of your service will become the DNS name that other pods use to access, in this example: <code>test-adminer-service</code>. If you scale your deployment up, then the service will load balance network traffic to all of your pods.
			* '''Log into your kubectl enabled terminal'''.
			* '''Create a new text file''' named <code>test-adminer-service.yml</code>. This file will describe your service as code.
			* Use the following code:
			<pre>
			apiVersion: v1
			kind: Service
			metadata:
			name: test-adminer-service
			namespace: my-test-namespace
			spec:
			ports:
			- name: tcp8080
			port: 8080
			protocol: TCP
			targetPort: 8080
			selector:
			deployment: test-adminer
			type: ClusterIP
			</pre>
			* '''Create your service''' using the following command:
			** <code>kubectl apply -f test-adminer-service.yml</code>

2023-11-27T21:04:22Z

Launch an App Using a Public Image

← Older revision		Revision as of 17:04, 27 November 2023
Line 132:		Line 132:
	restartPolicy: Always		restartPolicy: Always
	</pre>		</pre>
			* '''Launch your app''' using the following command:
			** <code>kubectl apply -f test-adminer.yml</code>