Welcome to oci-native-ingress-controller Discussions!

[nirpai]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[khchoy]

Hi,
Do you guys have any plan to merge this PR. I need this feature urgently. Thanks.
[Feature] Add extract-ca-from-tls-crt annotation (#60) #61

[nirpai]

I will prioritize this for a upcoming release.

[khchoy]

I will prioritize this for a upcoming release.

Is it possible to extend this feature to Load Balancer type Service's secret? For example, this annotation used by Service, i.e., "service.beta.kubernetes.io/oci-load-balancer-tls-backendset-secret"

[khchoy]

Hi I tested v1.3.7, still not up to my expectations.
Firstly, I pre-created a load balancer with a http listener (port 80) via terraform script and I assign the LB ocid to the IngressClass's annotation. IngressClass was installed. Then I deploy the Ingress resources with service port 443. My expectation is that I should have two listeners at the end of the deployment. Finally, everything created normally in the LB except the http listener (port 80) get deleted and ended up with only https listener (port 443) available. Why the http listener got deleted after Ingress resource deployment ended? Secondly, I took 2nd attempt and tried with these new annotation "oci-native-ingress.oraclecloud.com/http-listener-port: "80"" and "oci-native-ingress.oraclecloud.com/https-listener-port: "443"". I am expecting to have two listeners created at the end of the Ingress resource deployment. However, there is only one listener (port 443) get created. Why listener (port 80) not created in LB?

[khchoy]

I can't use Ingress resource with secret right now as it has limitation mentioned in this PR, #61. Wondering if this PR will be included in next release, i.e., v1.3.8?

[nirpai]

Hopefully yes. Will keep you posted.

[khchoy]

Hi, I saw this PR, #61 already been merged to main branch last two days. Can I test with latest main branch now or I still need to wait for official release?

[nirpai]

This will be part of our next release. We don't have an ETA for the release yet.

[nirpai]

Available now as part of 1.3.8