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

[Enhancement] Allow injection of custom Kubernetes Config or allow topologySpreadConstraints #192

Open
silvio201 opened this issue Mar 10, 2022 · 0 comments
Open

[Enhancement] Allow injection of custom Kubernetes Config or allow topologySpreadConstraints #192

silvio201 opened this issue Mar 10, 2022 · 0 comments

Comments

@silvio201
Copy link

Hello everyone,

I have the following situation.
I am deploying anchore on our OKD Cluster and integrating anchore scans with jenkins. We have 3 nodes and wanted to have 6 replicas of the anchore analyze pod in order to speed up the analyzing process.
Furthermore we want to deploy the 6 pods of the analyzer equally among the 3 nodes. Since this is not possible with podAntiAffinity it would be neat if the chart would offer the possibility to configure topologySpreadConstraints either by implementig it directly or by allowing to inject yaml directly into the deployment.

Thx in advance
Btodhunter pushed a commit that referenced this issue Feb 2, 2024
@HN23 @Btodhunter
updating error message for image_ttl_days (#192)
77114d7 
Signed-off-by: Hung Nguyen <[email protected]>
Btodhunter pushed a commit that referenced this issue Feb 2, 2024
@HN23 @Btodhunter
updating error message for image_ttl_days (#192)
4b3f392 
Signed-off-by: Hung Nguyen <[email protected]>
Btodhunter added a commit that referenced this issue Feb 2, 2024
@Btodhunter @HN23
stable/enterprise: Update Anchore Enterprise to v5.2.0 (#338)
903a0af 
* Ent 5.2.0 updates (#187)

* add additional configs for 5.2.0
* updating helm unittests and readme to include changes
* adding scratch for reports
* update default of api delete keys to 365; add scratch volume to reports pod; add reports resources tests
* adding additional reports resources test
* Enterprise split reports api (#188)
* move reports service to seperate deployment
* use enterprise prefix for helper templates
* add rbacAuth container back to api pod
* make reports-worker fullname match values key for the service
* update unit tests
* bump chart version
* fix reports worker descriptions & alphabetize the top level key
* add rbacAuth container to reports pod (#189)
* add rbacAuth container to reports pod
* add rbacAuth unit test for reports template
* updating error message for image_ttl_days (#192)
* Make scratch volume configurable (#193)
* use helper template for scratch volume details. Allow component specific configs
* add unit tests
* add necessary values and update readme
* bump chart version
* bump enterprise image to v5.2.0
* update test snapshots
* bump feeds chart version
* bump chart version
* update readme and values table
* remove reports service from the ingress configuration

---------

Signed-off-by: Brady Todhunter <[email protected]>
Signed-off-by: Hung Nguyen <[email protected]>
Co-authored-by: Hung Nguyen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@silvio201