Skip to content

Commit

Permalink
Allow upgrade Jobs to have Annotations (#97)
Browse files Browse the repository at this point in the history
In certain deployments, it is important to have control over the
annotations associated with an Upgrade Deployment. For example, if
primarily Fargate Pods are used in AWS, the upgrade jobs might need to
be run in EC2 context in order to speed up the helm upgrade process.

Signed-off-by: Adam Wallis <[email protected]>
  • Loading branch information
adawalli authored Dec 16, 2020
1 parent 4ffafb3 commit b06a85a
Show file tree
Hide file tree
Showing 5 changed files with 13 additions and 1 deletion.
2 changes: 1 addition & 1 deletion stable/anchore-engine/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v2
name: anchore-engine
version: 1.10.6
version: 1.10.7
appVersion: 0.8.2
description: Anchore container analysis and policy evaluation engine service
keywords:
Expand Down
3 changes: 3 additions & 0 deletions stable/anchore-engine/templates/engine_upgrade_job.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,9 @@ spec:
{{- with .Values.anchoreGlobal.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.anchoreEngineUpgradeJob.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
spec:
{{- with .Values.anchoreGlobal.securityContext }}
securityContext:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,9 @@ spec:
{{- with .Values.anchoreGlobal.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.anchoreEnterpriseFeedsUpgradeJob.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
spec:
{{- with .Values.anchoreGlobal.securityContext }}
securityContext:
Expand Down
3 changes: 3 additions & 0 deletions stable/anchore-engine/templates/enterprise_upgrade_job.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,9 @@ spec:
{{- with .Values.anchoreGlobal.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.anchoreEnterpriseEngineUpgradeJob.annotations }}
{{ toYaml . | nindent 8 }}
{{- end }}
spec:
{{- with .Values.anchoreGlobal.securityContext }}
securityContext:
Expand Down
3 changes: 3 additions & 0 deletions stable/anchore-engine/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -587,6 +587,7 @@ anchoreEngineUpgradeJob:
nodeSelector: {}
tolerations: []
affinity: {}
annotations: {}

# This section is used for configuring anchore enterprise.
anchoreEnterpriseGlobal:
Expand Down Expand Up @@ -709,6 +710,7 @@ anchoreEnterpriseFeedsUpgradeJob:
nodeSelector: {}
tolerations: []
affinity: {}
annotations: {}

# Configure the Anchore Enterprise role based access control component.
# This component consists of 2 containers that run as side-cars in the anchore engine api pod.
Expand Down Expand Up @@ -953,6 +955,7 @@ anchoreEnterpriseEngineUpgradeJob:
nodeSelector: {}
tolerations: []
affinity: {}
annotations: {}

# To inject secrets ( credentails data ) via env, rather k8s secrets please set this flag to true.
# This feature will be useful, especially to inject secrets directly into k8s pods from hashicorp vault
Expand Down

0 comments on commit b06a85a

Please sign in to comment.