- Formatting changes sky-uk#190
- Fix duplicate path when path is not specified sky-uk#193
- Remove unnecessary config reload after start up sky-uk#194
- Fix bug in v1.12.0 with the nginx.conf template sky-uk#188
- Enable overriding proxy buffer values. Defaults to
proxy_buffer_size 16k
andproxy_buffers 4 16k
Can be overridden with relevant annotations - The values overridden by the annotations are capped at a permissible max
proxy_buffer_size 32k
andproxy_buffers 8 32k
- Supports handling of large client requests (header and body). Refer https://github.com/sky-uk/feed#handling-large-client-requests
- DO NOT USE THIS VERSION
- Update nginx-opentracing version for bug fix to proxy headers
- Manually compile OpenTracing modules to avoid binary incompatibilities
- Add OpenTracing support
- Expose status updater error logs rather than printing a list of failed ingresses
- Bug fix for k8s/status updater where feed would exit the update loop if any ingress was 'unchanged'
- Added
merlin-internal-hostname
andmerlin-internet-facing-hostname
flags for setting Merlin ingress status, replacing themerlin-internet-facing-vip
flag - Included extra testing around ingress validation
- Added
k8s/status
library for setting ingress status - ELB and Merlin updaters set relevant ingress status
- Attach to https in addition to http for merlin.
- Fix merlin deregistration, which was failing due to long lived connections getting killed.
- Bug fix for merlin attacher - fix netlink and capabilities for feed-ingress.
- Introduced flag to set the amount of memory allocated to the vhost statistics module (default: 1 MiB)
- Add ability to specify health checks for merlin frontends.
- Upgraded to Nginx 1.12.2 and VTS 0.1.15
- Introduced
sky.uk/backend-max-connections
annotation that sets upstream.max_conns (http://nginx.org/en/docs/http/ngx_http_upstream_module.html#max_conns) - Introduced flag to set global value for upstream.max_conns (default: 1024)
- Add support for merlin frontend
- Swap to dep from govendor
- Moved to using pester as an http client
- Implemented retries on calls to the gorb API
- Enable SSL termination Set default ssl path + name file without extension. Feed expects two files: one ending in .crt (the CA) and the other in .key (the private key), for example: -ssl-path=/etc/ssl/default-ssl/default-ssl
- Add
gorb-backend-healthcheck-type
that can be either 'tcp', 'http' or 'none' - Remove deprecated
elb-drain-delay
feed-ingress flag
- Reduce logging each ingress in the controller from Info to Debug, introduced in v1.3.0
- Fix wrong output direction when managing loopback interface using sudo
- Add support for configuring IPVS via gorb with Direct Server Return packet-forwarding method.
Various flags prefixed with
gorb-
have been added to feed-ingress to customise gorb configuration. - Add
registration-frontend-type
feed-ingress flag to specify either elb, alb or gorb. - Deprecate
elb-drain-delay
feed-ingress flag in favour of the more genericdrain-delay
.
- Add support for non-AWS load balancers, which are referenced by static hostnames.
- Stop logging out the entire Route53 record set on update at Info in feed-dns: reduce this to Debug, and instead emit the number of records currently in the record set at Info
- Aggressively rotate access logs to avoid excessive file cache usage. This can lead to kernel allocation failures when running feed inside a container with a memory limit.
- Rename annotation
sky.uk/backend-keepalive-seconds
tosky.uk/backend-timeout-seconds
to make it clear that this value only affects request timeouts. The old annotation is preserved for backwards compatibility. - Update to golang 1.9.1.
- Fix bug where no ELB updater would be created if the
elb-label-value
is provided.
- Fix bug where feed-ingress would wait for
elb-drain-delay
andalb-target-group-deregistration-delay
even if no instances where attached. - Do not create ELB or ALB updater when
elb-label-value
oralb-target-group-names
, respectively, are empty. - Note: this image is broken, it does not create an ELB updater if the
elb-label-value
is provided.
Make deduping ingress entries deterministic.
The previous approach tried to order ingress by CreationTimestamp before picking the most recent ingress. This did not work because multiple duplicate ingresses could be created at the same time.
This fix orders ingress entries by Namespace,Name,Host,Path and only uses the first ingress 'Host/Path' encountered to dedupe. Kubernetes guarentees unique ingress for a given 'Namespace/Name' which will make this deduping deterministic.
- Do not delete unassociated resource record sets (http://github.com/sky-uk/feed/pull/144)
- Fix bug where feed-ingress could return 404s for a brief period upon startup.
- Fix bug in feed that causes unhealthy status at startup (sky-uk#141)
- First official release with our production-ready ingress controllers.