Configure auto_reload option of geoip2 module

kubernetes / ingress-nginx

Ingress NGINX Controller for Kubernetes

https://kubernetes.github.io/ingress-nginx/

Apache License 2.0

17.48k stars 8.25k forks source link

Configure auto_reload option of geoip2 module #8784

Closed mecseid closed 7 months ago

mecseid commented 2 years ago

What do you want to happen?

Manage the auto reload feature of GeoIP2 module: https://github.com/leev/ngx_http_geoip2_module#autoreload-default-disabled

Is there currently another issue associated with this?

https://github.com/kubernetes/ingress-nginx/issues/3629

Does it require a particular kubernetes version?

No.

k8s-ci-robot commented 2 years ago

@mecseid: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

mecseid commented 2 years ago

/remove-lifecycle stale

rikatz commented 8 months ago

/help /good-first-issue

Seems like the implementation of a configmap and setting it on nginx.tmpl

k8s-ci-robot commented 8 months ago

@rikatz: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/8784): >/help >/good-first-issue > >Seems like the implementation of a configmap and setting it on nginx.tmpl Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.