gke-autoneg-controller
gke-autoneg-controller copied to clipboard
This GKE controller provides simple custom integration between GKE and GCLB.
Kubernetes Service account is not being used by the role bindings
I ran into an issue where the autoneg controller service account is forbidden listing several kubernetes api resources. The autoneg-controller-manager pod is returning the following errors: ``` E0727 18:09:24.847396 1...
Update the installation step to add an annotation to configure the cluster side of workload identity. The installation step adds an annotation to the `default` service account in the `autoneg-system`...
The autoneg-controller-manager pod returns the following error when using workload identity: ``` 2022-07-27T18:52:41.739Z ERROR controller-runtime.controller Reconciler error {"controller": "service", "request": "/", "error": "googleapi: Error 401: Invalid Credentials, authError"} github.com/go-logr/zapr.(*zapLogger).Error /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:128...
Add tests that prove this case.
Updates to kubebuilder 3.1.0. kubebuilder 3.1.0 was used to create a new repo, made changes the new repo, and then merged back into the existing repo. Any non-cosmetic changes were...
Added support for regional -flag in addition to region parameter, as suggested in #41.
We deployed autoneg in one of our clusters running GKE Autopilot. When running a workload on it and if it's scheduled to just some specific zones but not all, the...
Removing config annotation `anthos.cft.dev/autoneg` still left the `anthos.cft.dev/autoneg-status` annotation, and also generated a `controller.autoneg.dev/neg-status` annotation. I would expect autoneg to deregister backends, remove the status annotation, and remove the finalizer.