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

First container name might not match service account #237

Closed
lkysow opened this issue Mar 27, 2020 · 1 comment · Fixed by #281
Closed

First container name might not match service account #237

lkysow opened this issue Mar 27, 2020 · 1 comment · Fixed by #281
Labels
area/connect Related to Connect service mesh, e.g. injection type/enhancement New feature or request

Comments

@lkysow
Copy link
Member

lkysow commented Mar 27, 2020

When using connect inject with ACLs, if the first container's name doesn't match the service account name then the consul login will fail and the service won't be registered. We should investigate some better logging or error messaging in this case. Or we could use the service account name instead of the first container's name.

@lkysow lkysow added area/connect Related to Connect service mesh, e.g. injection type/enhancement New feature or request labels Mar 27, 2020
@lkysow
Copy link
Member Author

lkysow commented Jun 10, 2020

Some error like: error: serviceAccountName "default" does not match service name "name" would be good to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connect Related to Connect service mesh, e.g. injection type/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant