You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add support for TCP pass-through listener without SSL
- Refactor SSL logic in ingressstate.go, filtering in routingpolicy.go
- Unit tests for changes
- Update GettingStarted.md
+[How to introduce new modules or upgrade existing ones?](#how-to-introduce-new-modules-or-upgrade-existing-ones)
39
41
*[Known Issues](#known-issues)
@@ -441,6 +443,7 @@ We will be able to configure ingress routes those are HTTPS enabled. Customers c
441
443
- In the case of Kubernetes secret we create a certificate service certificate and a ca bundle to configure the listener and backend set appropriately.
442
444
- In the case of certificates we use the certificate Id and certificate trust authority Id to configure listener and backend set.
443
445
- Customer can use the same credentials in their pods to make this an end to end SSL support.
446
+
- If the customer wishes to terminate TLS on the LB and run plain text (HTTP) backend, they can use the annotation `oci-native-ingress.oraclecloud.com/backend-tls-enabled: "false"` on the Ingress
444
447
445
448
##### Sample configuration : Using Secret
446
449
We create OCI certificate service certificates and cabundles for each kubernetes secret. Hence the content of the secret (ca.crt, tls.crt, tls.key) should conform to the certificate service standards.
is used in the Ingress resource, all hosts are considered TLS configured.
572
+
573
+
#### TCP Listener Support
574
+
Users can use the annotation `oci-native-ingress.oraclecloud.com/protocol: TCP` to configure the OCI LB Listeners created by NIC to be pass-through TCP listeners.
575
+
All TCP traffic to these listeners will be forwarded to specified backends. Note that any routing or TLS configuration for such an Ingress will be ignored.
576
+
577
+
An example Ingress can be seen below. Here, all traffic to port 8080 on the IngressClass backed OCI LB will be sent to `my-first-svc:8080`
578
+
and traffic on port 8081 of the LB will be forward to `my-second-svc:8081`.
579
+
```yaml
580
+
apiVersion: networking.k8s.io/v1
581
+
kind: Ingress
582
+
metadata:
583
+
name: ingress-pass-through
584
+
annotations:
585
+
oci-native-ingress.oraclecloud.com/protocol: TCP
586
+
spec:
587
+
rules:
588
+
- http:
589
+
paths:
590
+
- pathType: ImplementationSpecific
591
+
backend:
592
+
service:
593
+
name: my-first-svc
594
+
port:
595
+
number: 8080
596
+
- http:
597
+
paths:
598
+
- pathType: ImplementationSpecific
599
+
backend:
600
+
service:
601
+
name: my-second-svc
602
+
port:
603
+
number: 8081
604
+
```
605
+
606
+
550
607
### Dependency management
551
608
Module [vendoring](https://go.dev/ref/mod#vendoring) is used to manage 3d-party modules in the project.
0 commit comments