Skip to content

Conversation

@verma-kunal
Copy link
Contributor

@verma-kunal verma-kunal commented Sep 23, 2022

Signed-off-by: Kunal Verma [email protected]

Description

Adds a Deployment Helm-chart

Fixes #2389

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

I tested the chart locally with - helm template --debug . -f test_values.yaml
Here is the output file - output.txt

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have tested it for all user roles
  • I have added all the required unit/api test cases

Signed-off-by: Kunal Verma <[email protected]>
@verma-kunal verma-kunal marked this pull request as ready for review September 23, 2022 16:29
@gitguardian
Copy link

gitguardian bot commented Sep 23, 2022

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
- Generic High Entropy Secret 365dda5 contrib-chart/reference-chart_4-15-0/env-values.yaml View secret
- Generic High Entropy Secret 365dda5 contrib-chart/reference-chart_4-15-0/secrets-test-values.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@verma-kunal
Copy link
Contributor Author

cc @Abhinav-26

{{- end }}
selector:
app: {{ template ".Chart.Name .name" . }}
{{- if eq .Values.deploymentType "BLUE-GREEN" }}
Copy link
Contributor Author

@verma-kunal verma-kunal Sep 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{{- if eq .Values.deploymentType "BLUE-GREEN" }}

I believe this line needs to be deleted as I have deleted the deploymentType field fromtest_values.yaml
Would like to confirm first?!

Comment on lines +1 to +23
deployment:
strategy:
blueGreen:
autoPromotionSeconds: 30
scaleDownDelaySeconds: 30
previewReplicaCount: 1
autoPromotionEnabled: false
rolling:
maxSurge: "25%"
maxUnavailable: 1
canary:
maxSurge: "25%"
maxUnavailable: 1
steps:
- setWeight: 25
- pause:
duration: 15 # 1 min
- setWeight: 50
- pause:
duration: 15 # 1 min
- setWeight: 75
- pause:
duration: 15 # 1 min
Copy link
Contributor Author

@verma-kunal verma-kunal Sep 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this section also needs to be updated/changed as we are not using Rollout & by default the strategy type of Deployment resource is RollingUpdates. A bit unsure about this section though!
Would like any thoughts here.

@kartik-579 kartik-579 changed the base branch from deployment-chart-v0 to dynamic-templates November 17, 2022 07:52
@kartik-579 kartik-579 merged commit 37a6af1 into devtron-labs:dynamic-templates Nov 17, 2022
nishant-d pushed a commit that referenced this pull request Dec 14, 2022
* wip

* updated sql script

* fixed sql

* added spec

* Feat: Adding a Deployment Helm-chart (#2391)

* Add-deployment-chart

Signed-off-by: Kunal Verma <[email protected]>

* Update contrib-chart/reference-chart_4-15-0/templates/keda-autoscaling.yaml

Signed-off-by: Kunal Verma <[email protected]>

* renamed helm chart

* updated sql script for support of deployment type helm chart

* updated script no

* updated chart no

* added test cases

* fix sql

* fix

* review changes

* review changes - part 2

* updated down sql

* fix

* updated validation checks

* updated sql

* fixed required tag

* synced deployment chart with rollout-v4.16.0, renamed version

* updated log

* deployment chart changes

* fix for strategy type deployment

* updated deployment.yaml for deployment chart

* removed strategy check for pipeline trigger

* wip

* Removing strategy configs in case of Recreate

* Update pipeline-values.yaml

* updated sql script no.

* updated deployment.yaml

* removed deployment type chart as default

Signed-off-by: Kunal Verma <[email protected]>
Co-authored-by: Kunal Verma <[email protected]>
Co-authored-by: Prakarsh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants