- Jan 22, 2020
-
-
egon w. stemle authored
-
- Oct 25, 2019
-
-
egon w. stemle authored
-
- Oct 14, 2019
-
-
Alexander König authored
-
egon w. stemle authored
So far, we have used TLS certs from eurac's IT. Now, we (re-)use k8s infrastructure (in particular the kube-lego add-on) and let kube-lego - request/renew TLS certificates - manage the certificate within a k8s secret We then make this k8s secret available to our nginx and configure nginx to use it. We also got rid of internal TLS communication between ingress and the apps avoiding the necessity to (re-)create valid/self-signed certs. The overhead seemed unnecessary. Note: using HTTP(!) over port 443 for internal communication (Shibboleth mishap) Fix #62
-
- Jul 23, 2019
-
-
Alexander König authored
-
- Jul 01, 2019
-
-
Alexander König authored
-
- Feb 25, 2019
-
-
Alexander König authored
-
- Sep 06, 2018
-
-
egon w. stemle authored
- Sep 04, 2018
-
-
egon w. stemle authored
-
egon w. stemle authored
-
egon w. stemle authored
-
egon w. stemle authored
-
egon w. stemle authored
- disabled ssl-passthrough - configured ssl-certs FIXME: - repository/oai is not accessible via http - battle test the config
-
- Jun 15, 2018
-
-
Alexander König authored
- Jun 13, 2018
-
-
Alexander König authored
-
- Jun 12, 2018
-
-
egon w. stemle authored
- ingress also listens on port 80 - nginx redirects to https except for path: repository/oai
-
egon w. stemle authored
-
- May 18, 2018
-
-
Alexander König authored
-
- Feb 16, 2018
-
-
Alexander König authored
-
- Feb 01, 2018
-
-
Alexander König authored
variables to enable use of Kubernetes secrets - fixed TLS use in ingress - removed http/https redirect from nginx conf
-
- Jan 26, 2018
-
-
Alexander König authored
-
- Jan 18, 2018
-
-
Alexander König authored
-