Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make test-all-local fails getting credentials: exec: executable gke-gcloud-auth-plugin not found #2

Open
mikebz opened this issue May 24, 2022 · 4 comments
Assignees

Comments

@mikebz
Copy link
Contributor

mikebz commented May 24, 2022

Using make test-all-local

Error here:

/testing/nomos/e2e/setup.sh --preclean --setup --test --clean
Start setup.sh
e2e/setup.sh: executed with args --preclean --setup --test --clean
printing diagnostics
+ operator logs
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
+ importer pod
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
+ importer logs
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
++++ Cleaning up environment
+++++ Uninstalling
++++ Waiting for environment cleanup to finish
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found

It looks like you are trying to use a client-go credential plugin that is not installed.

To learn more about this feature, consult the documentation available at:
      https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
### e2e tests failed. Temp dir (with test output logs etc) are available in /usr/local/google/home/mikebz/src/kpt-config-sync/.output/tmp
make[1]: *** [Makefile.e2e:50: __test-e2e-run] Error 1
make[1]: Leaving directory '/usr/local/google/home/mikebz/src/kpt-config-sync'
make: *** [Makefile.e2e:102: test-e2e] Error 2

I do have the gke-gclod-auth-plugin locally and followed the steps:
https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

@rquitales
Copy link
Contributor

The issue is that the test, and kubectl commands, are run within a container. The gke-gcloud-auth-plugin needs to be installed within the container image that is running the e2e tests, whereas you have the auth plugin installed locally. The Dockerfiles will need to be updated to install the auth plugins.

The following file will need to be updated.

gcloud components install alpha beta

We can use gcloud components install gke-gcloud-auth-plugin, but this requires also updating the gcloud version used in the test container since it's on v255, and a newer gcloud version is required to install this component. Alternatively, we can also use the Debian apt-get commands to install this instead.

@karlkfi
Copy link
Contributor

karlkfi commented Apr 6, 2023

@sdowell @mikebz Is this fixed now with the recent merge of #514 ?

@mikebz
Copy link
Contributor Author

mikebz commented Apr 7, 2023

wanted to verify this, but it looks like there is another error. Just got latest and ran make clean and then make test-all-local

Output:

...
W0407 03:46:32.024213    1436 library.go:94] "github.com/klauspost/compress/zstd/internal/xxhash" contains non-Go code that can't be inspected for further dependencies:
/go/src/kpt.dev/configsync/vendor/github.com/klauspost/compress/zstd/internal/xxhash/xxhash_amd64.s
W0407 03:46:32.029607    1436 library.go:94] "github.com/klauspost/compress/zstd" contains non-Go code that can't be inspected for further dependencies:
/go/src/kpt.dev/configsync/vendor/github.com/klauspost/compress/zstd/fse_decoder_amd64.s
/go/src/kpt.dev/configsync/vendor/github.com/klauspost/compress/zstd/seqdec_amd64.s
go install github.com/google/[email protected]
GOBIN=/usr/local/google/home/mikebz/go/bin ./scripts/license-headers.sh lint
make: *** No rule to make target 'test-e2e', needed by 'test-all-local'.  Stop.

@sdowell
Copy link
Contributor

sdowell commented Apr 7, 2023

Looks like a forgotten make target, I can make a PR to clean that up. Up to date instructions on how to run the e2e tests can be found here: https://github.com/GoogleContainerTools/kpt-config-sync/blob/main/docs/development.md

tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 28, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 28, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 29, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 29, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 29, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 30, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 30, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue May 31, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
tiffanny29631 added a commit to tiffanny29631/kpt-config-sync that referenced this issue Jun 3, 2024
The metric name was changed to `declared_resources_total` using the metricstransform processor without communicating in the documentation / release note and the intention was unclear.

This change reverts the name change and adds e2e test around all the [available metrics](http://cloud/kubernetes-engine/enterprise/config-sync/docs/how-to/monitoring-config-sync) in GCM. The check skips the counter metrics for now as they have no data when no error condition has happened.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants