-
Notifications
You must be signed in to change notification settings - Fork 27
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
Hooks pro pods add image pull secrets #338
base: main
Are you sure you want to change the base?
Conversation
Added Hooks example for adding `imagePullSecrets` to all vCluster workload pods.
✅ Deploy Preview for vcluster-docs-site ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Could you please allow edits by maintainers, so I can help you with |
Removed all 'we'
Removed the word 'functionality'
The Vale issue is related to using "Hooks (Pro)". I believe we use this formatting in multiple places. If we are going to change it to satisfy Vale, what should it be changed to? "Hooks (pro)"? Also, can't add comment in source as this Vale issue is for something that was not changed in the PR. |
remove 'an' from 'for an examples'
@kmadel, apologies for back and forth on this one, I had to add the vale exception in different file. If you rebase again the rule should work correctly. |
Although the vCluster vcluster.yaml configuration provides the workloadServiceAccount that allows including
imagePullSecrets
, it is limited as thatserviceAccount
is superseded when usingsync.toHost.pods.serviceAccounts.enabled: true
.This allows setting
imagePullSecrets
at the pod level instead of via aserviceAccount
- although it does rely on a Pro feature.