shipper
shipper copied to clipboard
Kubernetes native multi-cluster canary or blue-green rollouts using Helm
One of the key feature of k8s, [horizontal pod scaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) is in conflict with the current shipper's capacity management strategy. In real life our users over-provision resources with a tremendous...
Shipper now uses Endpoints to check for traffic progression (#238), which is an improvement over just checking that pods got their labels. If pods don't make it into the Endpoints...
Currently Shipper only understands that clusters are running in "regions". It also has an implicit assumption that multiple clusters inside the same region are running in different availability zones. Moving...
Some of the Kubernetes clients use clients generated from a swagger.json. kubernetes-client/javascript uses kubernetes-client/gen which uses OpenApiTools/openapi-generator and kubernetes/kubernetes/api/openapi-spec/swagger.json There are open/closed/rotten/ignored issues all over the place about making these...
Suggestions for updates to webhook: * In kubernetes version 1.16, admissionregistration/v1beta1 will be deprecated in favor of admissionregistration.k8s.io/v1. We need to update shipperctl code. * Timeouts. From the docs: Because...
As Helm has transitioned v3 to a stable state, we might consider testing shipper against this new version as from now on, new features would be only delivered to v3:...
This commit changes the behavior of the makefile and removes the release tag from file names. This is mainly done to preserve a deterministic path to shipper deploy file which...
# What >AS A user of Kubernetes Clusters to manage my workloads using [`kubectl`](https://github.com/kubernetes/kubectl) > GIVEN I have kubectl installed on my workstation and my build-environment >WHEN I need to...
Rolling out a new version of an application is very implicit in our documentation, an user needs to be familiar enough with kubernetes to realize that you need to change...
As our document said, shipper support multi-cluster/multi-region natively, but I don't know what it means, like the following spec: ``` clusterRequirements: regions: - name: local ``` what's the process would...