Awesome. I think I might have also found a possible miss configuration in the annotations. I’ll gather more info and raise a bug if so. What component of it is a bug?
It’s most likely a charm bug since the only annotations Juju adds are to record the controller and model UUIDs. Perhaps post the details here ans we can figure out where the issue lies.
Sticking with the HTTPS part of the thread, I feel like I’m missing something here. Doesn’t the TLS part secure the client -> nginx part of the conversation with a specific set of certificates? I’m specifically looking to use HTTPS from nginx -> backend service port, and this does not seem to be changing anything. Specifically, I thought I just needed to add nginx.ingress.kubernetes.io/backend-protocol: “HTTPS” to the annotations.
If I use the name of the container as the name of the ingress resource, it tells me that it is a juju reserved name and does not create it. If I use this, the config is created, but does not seem to get activated in nginx.