-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CronJob should curl service name rather than ingress host #16
Comments
Signed-off-by: elonzh <elonzh@qq.com>
This does not work for me @elonzh
|
If the chart is deployed with an ingress the cronjob calls the ingress. There's no reason for the cronjob to ever call the ingress, it's deployed inside the cluster so it should call the service by name, always. I'll test and PR a fix for the case of ingress on when I have time. |
Yes, the above theory should work, except it doesn't. See my comment above. I suspect that is because of the |
If we would be able to dynamically configure |
Current template:
helm/charts/nextcloud/templates/cronjob.yaml
Lines 45 to 56 in 1cb0e7a
The problems:
.Values.ingress.tls
is not the only approach to set httpsThe solution:
just curl the service name and service port, like this:
if we use this solution,
.Values.cronjob.curlInsecure
can be removed.The test:
The text was updated successfully, but these errors were encountered: