Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

[Nginx ingress controller] Annotations configuration in ingress #2044

Closed
timactive opened this issue Nov 16, 2016 · 4 comments · Fixed by kubernetes/ingress-nginx#148
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@timactive
Copy link

timactive commented Nov 16, 2016

Add new anotations for nginx config in ingress

This annotation must override config in configmap.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 name: docker-registry
 namespace: devops
 annotations:
   ingress.kubernetes.io/cg-body-size: "600M"
   ingress.kubernetes.io/cg-server-name-hash-bucket-size: "64"
   ingress.kubernetes.io/cg-server-name-hash-bucket-size: "64"
spec:
  tls:
  - hosts:
    - registry.example.com
    secretName: registry-example-tls
  rules:
    - host: registry.example.com
      http:
        paths:
        - path: /
          backend:
            serviceName: docker-registry-sv
            servicePort: 5000
@timactive timactive changed the title Annotation configuration in ingress Ingress controller / Nginx / Annotations configuration in ingress Nov 16, 2016
@timactive timactive changed the title Ingress controller / Nginx / Annotations configuration in ingress [Nginx ingress controller] Annotations configuration in ingress Nov 16, 2016
@aledbf
Copy link
Contributor

aledbf commented Nov 16, 2016

@timactive in the next release is not required to configure to configure server-name-hash-bucket-size. because the ingress controller will calculate the value for you.

ingress.kubernetes.io/cg-body-size: "600M"

Added to the todo list. The name will be ingress.kubernetes.io/body-size: "600M"

@timactive
Copy link
Author

timactive commented Nov 16, 2016

@aledbf > Added to the todo lis
Super 👍

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants