-
Notifications
You must be signed in to change notification settings - Fork 9
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
Stage: Deploy Improvements #43
Comments
Helm uses a similar approach for their values/templates - https://github.com/kubernetes/helm/blob/master/docs/charts.md#templates-and-values |
For variables we can use gotemplate and toml to provide the values. - name: Deploy App
type: deploy
params:
deploy_file: manifest.yml
value_file: manifest.toml If value_file is left empty, then will run/apply manifest.yml as is. |
A few alternatives to consider too... KVs in the yaml: - name: Deploy App
type: deploy
params:
deploy_file: manifest.yml
vars:
value1: something
value2: somethingelse or otherwise ConfigMaps One consideration with any of these options is how do we handle/specify global variables (commit id, tags, etc) or pass vars them between stages |
for approach 1 these are the sample files: manifest.yml
manifest.toml
|
we can add |
Opened PR #53 for discussions... |
initial list of Kontinuous variables to be exposed to the user
|
These will be keys of the pipeline vars and ENV vars? "KONTINUOUS_REQUIRE_SOURCE_CODE" what does this do? |
it's use in the kontinuous agent to |
Why is it needed globally? |
i don't think we'll be needing that soon. |
the list is just partial. we can cherry-pick on what would be useful to the user. |
Fixes #53
Added support for global and local vars |
Does this also include the Kontinuous variables? |
yes. |
LGTM! |
can we close this? |
The deploy stage is a good start but there are some improvements needed to be useful for real deployments.
<basenamespace>-staging
or<basenamespace>-<commitid>
). Regex/Variable support useful here too?kubectl apply
support - updating existing resources in placePerhaps it is easier to use
kubectl
directly for the stage instead of the APIA few of these ideas are coming from the GCE CD Jenkins example (https://github.com/GoogleCloudPlatform/continuous-deployment-on-kubernetes/blob/master/sample-app/Jenkinsfile#L39-L48)
The text was updated successfully, but these errors were encountered: