-
Notifications
You must be signed in to change notification settings - Fork 14
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
Configuration for Privileged vs Non-Privileged services #205
Comments
The current release of Assemblyline lets you add labels on a per-container basis in the service settings. This wouldn't let you blanket apply the label without some scripting on your end, but does give you the specificity to avoid applying the label were you don't want it. Feedback? |
Might you be able to provide an example of how you might apply a label, for example Also, perhaps another ticket, but might we be able to use this service section to define a service's |
+1 for documentation update :) |
Is your feature request related to a problem? Please describe.
Our Elastic instance requires a pod label to access it. I am unable to configure a label privileged services in order to access these resources without granting similar access to non-privileged services.
Describe the solution you'd like
Please provide a configuration for adding labels to privileged vs non services. Perhaps a section similar to
config.scaler.additional_labels
Additional context
These are the update services that I need to provide access to Elastic for function, which in my environment, requires a pod label.
The text was updated successfully, but these errors were encountered: