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

Change image repository override information error log level #768

Open
wjun opened this issue May 10, 2024 · 0 comments
Open

Change image repository override information error log level #768

wjun opened this issue May 10, 2024 · 0 comments
Labels
kind/bug PR/issue related to a bug needs-triage

Comments

@wjun
Copy link

wjun commented May 10, 2024

Bug description
We use pinniped with an oidc test user to create a context. During the login process, one information(in black) shown below which will confuse users:
anzu context create mgmte --endpoint=https://192.168.120.1 --insecure-skip
-tls-verify
[ok] successfully created a kubernetes context using the kubeconfig /root/.kube/config
[i] Checking for required plugins for context 'mgmte'...
[i] unable to get image repository override information for some of the plugins. Error: configmaps is forbidden: User "johndoe@example.com" cannot list resource "configmaps" in API group "" in the namespace "tanzu-cli-system"

Because there is no tanzu-cli-system on our k8s cluster, and there is no image repository override settings at all, so users cannot understand what this information means.

Expected behavior
The above error message should not show, or at least, the log level at

log.Infof("unable to get image repository override information for some of the plugins. Error: %v", err)
should not be the default one.

Steps to reproduce the bug / Relevant debug output

Output of tanzu version
All versions.
Environment where the bug was observed (cloud, OS, etc)

@wjun wjun added kind/bug PR/issue related to a bug needs-triage labels May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug PR/issue related to a bug needs-triage
Projects
None yet
Development

No branches or pull requests

1 participant