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
When I tried to deploy the ocis-charts to k3s running on a remote machine I had to tell CoreDNS how to resolve domains like ocis.kube.owncloud.test to the host raspbian-bullseye-arm64. To authenticate users via OIDC, the proxy service has to be able to resolve the extarnalDomain:ocis.kube.owncloud.test. While I found out how to solve it, the below snippet should be added to documentation. But where?
Looking at the K3S CoreDNS config we can see that it imports *.override files.
When I tried to deploy the ocis-charts to k3s running on a remote machine I had to tell CoreDNS how to resolve domains like
ocis.kube.owncloud.test
to the hostraspbian-bullseye-arm64
. To authenticate users via OIDC, the proxy service has to be able to resolve theextarnalDomain:ocis.kube.owncloud.test
. While I found out how to solve it, the below snippet should be added to documentation. But where?Looking at the K3S CoreDNS config we can see that it imports
*.override
files.Googling how to provide them we can find MS Docs on how to customize CoreDNS.
Since we want to point all
*.kube.owncloud.test
domains to the host, we can use CorDNS rewrite plugin like this:Replace
raspbian-bullseye-arm64
with your hostname and(.*).kube.owncloud.test
with a regex for the domains you want to point back to the host.Apply the config and restart CoreDNS:
Finally, test that you can now resolve the domain:
Profit!
The text was updated successfully, but these errors were encountered: