Tags: nstott/voyager
Tags
Release 3.1.0 - Create RBAC roles for Voyager pods voyagermesh#256 (tamalsaha) - Add configure option for Haproxy default timeout. voyagermesh#286 (sadlil) - Supports setting resource for pods voyagermesh#277 - Install Voyager as critical addon voyagermesh#292 - Document HorizontalPodAutoscaling for HAProxy pods voyagermesh#242 - Record events against TPR voyagermesh#79 - Bug: Sets topology key for pod anti-affinity voyagermesh#320 - Bug: ServiceMonitors are restored if deleted by mistake. voyagermesh#283 - Bug: HostPort mode fixed work for AWS voyagermesh#281 - Bug: Externalservice redirection does not reset anymore voyagermesh#279 - Bug: Voyager works with cloud = minikube and type = HostPort voyagermesh#272 - Bug: Adding cert manager to existing ingress opens port 443 voyagermesh#267 - Bug: Annotations are applied properly voyagermesh#266 - Bug: Always add newline in pem file voyagermesh#261 - Bug: Adding SSL to an existing ingress correctly mounts certs voyagermesh#260 - Bug: Correctly detect changed ports voyagermesh#322 (tamalsaha) - Bug: Fixed Operator panic on service restore voyagermesh#273 (sadlil) - Bug: Deletes TPR when Kubernetes namespace is deleted voyagermesh#258 - Removed event frameworks codebase voyagermesh#282 (tamalsaha)
Release 3.0.0 - Use client-go 3.0.0 - Use HAProxy 1.7.6 - Use Kloader 3.0.0 - Stop creating stats service. - Automatically create ServiceMonitor for built-in exporter - Update labels applied to HAProxy pods & services. - Uses pod anti-affinity for deployments because we want to spread the HAProxy replicas for an ingress across different nodes. - Remove deprecated Daemon type. - Change api group to voyager.appscode.com - Released binaries are now reproducible. - Change default ports. - Pass cloud config using --cloud-config flag. - Open both port 443 & 80 when AWS cert manager is in use. - Add dns-resovler-check-health annotation for ExternalName service - Delete pods & services matching deprecated labels before starting operator
Release 1.5.6 Notable Features: - [Supports Loadbalancer Source Range](docs/user-guide/ingress/source-range.md) - [Supports redirects/DNS resolution for `ExternalName` type services](docs/user-guide/ingress/external-svc.md) - [Expose HAProxy stats for Prometheus](docs/user-guide/ingress/stats-and-metrics.md) - [Supports AWS certificate manager](docs/user-guide/ingress/aws-cert-manager.md) - Preserve source IP for LoadBalancer type Ingress using `ingress.appscode.com/keep-source-ip` annotation key. - Voyager operator collects anonymous usage statistics to help us learn how the software is being used and how we can improve it. To disable stats collection, run the operator with the flag `--analytics=false`. - Loadbalancer hostname is now added to Ingress status. - Kloader updated to 1.5.1 and Kloader now checks Kubernetes api server connection & kloader args before starting runit. - Voyager opreator now watches for deleting of service, deployment, daemonSet for any ingress managed by it. Voyager undos deletion of these resources, if the source ingress exists. - Various modification has been made to Voyager chart based on feedback from official Charts team. - Annotation keys has been updated to use format `ingress.appscode.com/w1-w2-w3`. Annotation values format has also updated. Please see [here](https://github.com/appscode/voyager/tree/1.5.6/docs/user-guide/ingress#configuration-options). - `HostPort` type Ingress will error out if node selector is missing. - Voyager deployment instruction now runs Voyager operator in `kube-system` namespace.
Release 1.5.5 - [Weighted Loadbalancing for Canary Deployment](docs/user-guide/component/ingress/weighted.md) - [Customize generated HAProxy config via BackendRule](docs/user-guide/component/ingress/backend-rule.md) - [Add Custom Annotation to LoadBalancer Service and Pods](docs/user-guide/component/ingress/annotations.md) - TLS tickets are disabled to ensure forward secrecy - Multiple replicas of HAProxy can be run using `ingress.appscode.com/replicas` annotation on ingress. If not set, this defaults to 1. - Instead of ReplicationController, Voyager now used Deployments with `LoadBalancer` type ingress. - A new mode called `NodePort` has been added that exposes HAProxy using a `NodePort` type service. This can be used in bare metal cluster to provide fault tolerance. - Daemon type has been renamed to HostPort in docs. If you have an existing `Daemon` type ingress, it will continue to work. - HAProxy version has been upgraded to 1.7.5 - Base image for voyager pod has been updated to alpine. - Update of ingress resources are handled such that unnecessary updates to firewalls are avoided with cloud providers like `aws`, `gce`, `gke` and `azure`.
Release 1.5.3 - Ingress Hostname based traffic forwarding (voyagermesh#66) … - cloud-provider & cloud-name is not required for unknown providers. (voyagermesh#65)