8 Commits

Include renames

Author	SHA1	Message	Date
Stefan Prodan	cd75c5fa25	Copyright Flux authors ... Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	2020-12-21 19:44:52 +02:00
Stefan Prodan	90abb7ba5b	Rename imports to fluxcd/flagger ... Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	2020-12-21 19:02:23 +02:00
mathetake	ef8b6fe9b8	finalizer: refactoring	2020-03-29 17:07:18 +09:00
Tanner Altares	92937a8f48	kubectl annotation support ... rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller add unit tests for finalizing introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller run fmt to clean up formatting review changes add kubectl annotation add kubectl annotation support introduction of finalizer introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller add unit tests for finalizing introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller run fmt to clean up formatting review changes introduction of finalizer introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller add unit tests for finalizing introduction of finalizer rebase and squash fix fmt issues revert Dockerfile revert go.mod and go.sum introduction of finalizer introduction of finalizer remove test for finalizer add istio tests fix fmt issues revert go.mod and go.sum revert Dockerfile and main.go fmt deployment controller run fmt to clean up formatting review changes	2020-03-20 15:13:51 -05:00
mathetake	23ab1bdb4b	pkg/router: improve error handling messages	2020-03-08 11:45:09 +09:00
stefanprodan	448c210324	Release API version v1beta1 ... - bump Canary and MetricTemplate version to v1beta1 - regenerate clientset and CRD	2020-02-07 12:35:56 +02:00
stefanprodan	8766523279	Add initialization phase to Kubernetes router ... Create Kubernetes services before deployments because Envoy's readiness depends on existing ClusterIPs	2019-11-27 22:15:04 +02:00
Yusuke Kuoka	e1d8703a15	Refactor to merge KubernetesServiceRouter into ServiceController ... The current design is that everything related to managing the targeted resource should go into the respective implementation of `canary.Controller`. In the service-canary use-case our target is Service so rather than splitting and scattering the logics over Controller and Router, everything should naturally go to `ServiceController`. Maybe at the time of writing the first implementation, I was confusing the target service vs the router.	2019-11-27 22:40:40 +09:00