Add TektonCD pipeline #63
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pst
commented
Jun 27, 2019
pst
force-pushed
the
pipeline
branch
4 times, most recently
from
a2542f9
to
729d879
Compare
0.12.6 seems to fix the errors when running TF with Google's new workload identity.
Having all cluster pairs in one TF configuration makes hard or even impossible to have each cluster apply its own configuration during the in-cluster Tekton run. * This PR splits the tests into one subdirectory per cluster pair. * It also puts the state for each cluster pair into the respective provider's object store.
pst
commented
Aug 26, 2019
| @@ -5,10 +5,9 @@ locals { | |||
|
|
|||
| workspace_label = "${var.label_namespace}cluster_workspace" | |||
| workspace = var.metadata_labels[local.workspace_label] | |||
| build_path = "manifests/overlays/${var.cluster_type}/${local.workspace}" | |||
| build_path = "../manifests/overlays/${var.cluster_type}/${local.workspace}" | |||
There was a problem hiding this comment.
TODO: Remember to change directory layout in quickstart too.
pst
commented
Aug 26, 2019
pst
commented
Aug 26, 2019
| @@ -0,0 +1,8 @@ | |||
| terraform { | |||
| backend "azurerm" { | |||
| resource_group_name = "terraform-kubestack-testing" | |||
There was a problem hiding this comment.
TODO: Update quickstart to also include resource_group_name and update instructions too.
This workflow is necessary to prevent the bootstrap failing when applying the pipeline manifests before TektonCD CRDs have been created successfully. The pipeline will in any case always need the repository, host-key and in most cases a ssh private-key to access private repositories. User bootstrap worklow will most likely be: 1. local repository 2. bootstrap ops and apps clusters 3. push local repository to remote 4. link clusters to repository
|
I'm stopping the effort to move the automation inside each cluster using Tekton, because there is no good solution to handle potential delete/recreate or destroy scenarios from within the cluster itself. Tekton is very complex and the above limitation means it does not add enough value to justify the maintenance effort it requires. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.