1
0
Fork 0
kubernetes/websites
Dustin a443929c0c websites: Manage dcow cert via Ingress annotation
Now that the reverse proxy for Internet-facing sites uses TLS
passthrough, the certificate for the _darkchestofwonders.us_ Ingress
needs to be correct.  Since Ingress resources can only use either the
default certificate (_*.pyrocufflink.blue_) or a certificate from their
same namespace, we have to move the Certificate and its corresponding
Secret into the _websites_ namespace.  Fortunately, this is easy enoug
to do, by setting the appropriate annotations on the Ingress.

To keep the existing certificate (until it expires), I moved the Secret
manually:

```sh
kubectl get secret dcow-cert -o yaml | grep -v namespace | kubectl create -n websites -f -
```
2024-08-24 11:30:56 -05:00
..
darkchestofwonders.us websites: Manage dcow cert via Ingress annotation 2024-08-24 11:30:56 -05:00
kustomization.yaml websites: Host darkchestofwonders.us in k8s 2024-01-04 08:56:12 -06:00
namespace.yaml websites: Host darkchestofwonders.us in k8s 2024-01-04 08:56:12 -06:00
secrets.yaml websites: Host darkchestofwonders.us in k8s 2024-01-04 08:56:12 -06:00