Ingress backends - Revision history

Busk at 14:12, 19 April 2023

2023-04-19T14:12:48Z

Busk at 20:10, 23 October 2022

2022-10-23T20:10:49Z

Busk at 20:08, 23 October 2022

2022-10-23T20:08:53Z

Busk at 20:03, 23 October 2022

2022-10-23T20:03:43Z

Busk at 20:03, 23 October 2022

2022-10-23T20:03:03Z

Busk at 20:01, 23 October 2022

2022-10-23T20:01:03Z

Busk at 19:58, 23 October 2022

2022-10-23T19:58:14Z

Busk at 19:50, 23 October 2022

2022-10-23T19:50:28Z

Busk: Created page with "https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/"

2022-10-23T19:48:40Z

Created page with "https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/"

New page

https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/

← Older revision		Revision as of 14:12, 19 April 2023
Line 71:		Line 71:
	servicePort: "80"		servicePort: "80"

		+	```
		+
		+	```
		+
		+	Subdir exact
		+	---
		+	apiVersion: networking.k8s.io/v1
		+	kind: Ingress
		+	metadata:
		+	name: monitor-utils-subdir
		+	annotations:
		+	# nginx.ingress.kubernetes.io/configuration-snippet: \|
		+	# if ( $arg_proxyToken != "hytokentext" ) {
		+	# return 401 'Unauthorized proxy token!';
		+	# }
		+	nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
		+	nginx.ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/8
		+	nginx.ingress.kubernetes.io/rewrite-target: /$2
		+	spec:
		+	ingressClassName: nginx
		+	tls:
		+	- hosts:
		+	- monitor.mktp.io
		+	secretName: tls-monitor-example-com
		+	rules:
		+	- host: monitor.example-com
		+	http:
		+	paths:
		+	- path: /monitor-utils(/\|$)(.*)
		+	# - path: /monitor-utils/
		+	pathType: Exact
		+	backend:
		+	service:
		+	name: monitor-utils
		+	port:
		+	number: 8080
	```		```

← Older revision		Revision as of 20:10, 23 October 2022
Line 1:		Line 1:
	https://kubernetes.io/docs/concepts/services-networking/service/		https://kubernetes.io/docs/concepts/services-networking/service/
		+
		+	https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
		+

	https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/		https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/

← Older revision		Revision as of 20:08, 23 October 2022
Line 1:		Line 1:
		+	https://kubernetes.io/docs/concepts/services-networking/service/
		+
	https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/		https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/

← Older revision		Revision as of 20:03, 23 October 2022
Line 10:		Line 10:

	https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/		https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/
		+
		+	.spec.clusterIP must be "None"

← Older revision		Revision as of 20:03, 23 October 2022
Line 8:		Line 8:

	https://link.medium.com/O66JLckTmub		https://link.medium.com/O66JLckTmub
		+
		+	https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/
		+
		+
		+
		+

← Older revision		Revision as of 20:01, 23 October 2022
Line 7:		Line 7:
	https://kubernetes.io/docs/concepts/services-networking/service/#headless-services		https://kubernetes.io/docs/concepts/services-networking/service/#headless-services

−		+	https://link.medium.com/O66JLckTmub

← Older revision		Revision as of 19:58, 23 October 2022
Line 3:		Line 3:

	https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/#using-external-ip		https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/#using-external-ip
		+
		+
		+	https://kubernetes.io/docs/concepts/services-networking/service/#headless-services
		+
		+
		+

	```to collect data to improve your experience on our site, as described in our Privacy Policy.		```to collect data to improve your experience on our site, as described in our Privacy Policy.

← Older revision		Revision as of 19:50, 23 October 2022
Line 1:		Line 1:
	https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/		https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/
		+
		+
		+	https://voyagermesh.com/docs/10.0.0/guides/ingress/http/external-svc/#using-external-ip
		+
		+	```to collect data to improve your experience on our site, as described in our Privacy Policy.
		+
		+	You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.
		+	New to Voyager? Please start here.
		+
		+	Using External Service as Ingress Backend
		+	You can use an external service as a Backend for Kubernetes Ingress. There are 2 options depending on whether the external service has an external IP or DNS record.
		+
		+	Using External IP
		+	You can introduce any external IP address as a Kubernetes service by creating a matching Service and Endpoint object. Then you can use this service as a backend for your Ingress rules.
		+
		+	apiVersion: v1
		+	kind: Service
		+	metadata:
		+	name: external-ip
		+	spec:
		+	ports:
		+	- name: app
		+	port: 80
		+	protocol: TCP
		+	targetPort: 9855
		+	clusterIP: None
		+	type: ClusterIP
		+	---
		+	apiVersion: v1
		+	kind: Endpoints
		+	metadata:
		+	name: external-ip
		+	subsets:
		+	- addresses:
		+	# list all external ips for this service
		+	- ip: 172.17.0.5
		+	ports:
		+	- name: app
		+	port: 9855
		+	protocol: TCP
		+	Now, you can use this external-ip Service as a backend in your Ingress definition. For example:
		+
		+	apiVersion: voyager.appscode.com/v1beta1
		+	kind: Ingress
		+	metadata:
		+	name: test-ings-rhvulnlb
		+	namespace: test-x
		+	spec:
		+	backend:
		+	serviceName: external-ip
		+	servicePort: "80"
		+
		+	```