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.

Sign up for GitHub

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

Jump to bottom

Optionally set service account of chaincode pods #76

Closed
jt-nti opened this issue Dec 8, 2022 · 1 comment
Closed

Optionally set service account of chaincode pods #76

jt-nti opened this issue Dec 8, 2022 · 1 comment
Labels
enhancement New feature or request
Milestone
Version 1

Comments

@jt-nti
Copy link
Member

jt-nti commented Dec 8, 2022

Chaincode pods are currently created without specifying a service account which means that they are automatically assigned the default service account. To pull chaincode images this service account may require an image pull secret to be defined - see #65 - which may not be desirable on the default service account.

Add a new FABRIC_K8S_BUILDER_SERVICE_ACCOUNT option similar to the existing FABRIC_K8S_BUILDER_NAMESPACE to allow a different service account to be specified if required.
@jt-nti jt-nti added the enhancement New feature or request label Dec 8, 2022
@jt-nti jt-nti mentioned this issue Jan 6, 2023
Closed
8 tasks
@jt-nti jt-nti added this to the Version 1 milestone Jan 6, 2023
@jt-nti
Copy link
Member Author

jt-nti commented Jan 26, 2023

Fixed in #77

@jt-nti jt-nti closed this as completed Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Version 1
Development

No branches or pull requests
1 participant
@jt-nti