RFC - Enterprise Bootstrapping #101
Open
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
enekofb
commented
Jan 10, 2023
| 4. it shoudl works with 'any' infrastructure layer (ex not only work with terraform | ||
| provisioned infra not just capi provisioned infra) | ||
|
|
||
| ### alternative a: leverage terraform for configuration manager |
There was a problem hiding this comment.
to validate with @JamWils whether aligns with the product strategy for weave gitops
enekofb
commented
Jan 10, 2023
|
|
||
| ### alternative a: leverage terraform for configuration manager | ||
|
|
||
| Same approach as take for cluster bootstrap controller but leveraging terraform and terraform controller |
There was a problem hiding this comment.
From @MostafaMegahid policy agent needs cert manager, how to provision this?
enekofb
commented
Jan 10, 2023
| ### alternative a: leverage terraform for configuration manager | ||
|
|
||
| Same approach as take for cluster bootstrap controller but leveraging terraform and terraform controller | ||
| for bootstrapping via terraform doing the configuration management. |
There was a problem hiding this comment.
policy agent is used for validate infrastructure - is there a chicken and egg solution?
enekofb
commented
Jan 10, 2023
|
|
||
| - infrastructure should not be linked to cluster api | ||
|
|
||
| ### alternative b: same as a) but via cluster bootstrapping |
There was a problem hiding this comment.
@ahsayde if you want to complete
enekofb
commented
Jan 18, 2023
|
|
||
| TBA | ||
|
|
||
| ### alternative c: do nothing, leverage to CRE |
There was a problem hiding this comment.
@ahsayde could you add the alternative https://weaveworks.slack.com/archives/C04JB21RCRK/p1674042182749089
here?
enekofb
changed the title
enekofb
force-pushed
the
bootstrapping-next
branch
from
c39c683 to
f0bbbfa
Compare
| namespace: flux-system | ||
| ``` | ||
|
|
||
| A PoC could be found [here](https://github.com/weaveworks/clusters-config/tree/cluster-wge2205/) |
There was a problem hiding this comment.
Blockers and manual work
- needs to apply flux namespace first more info here
- tf-controller needs service account to work in case of aws or gke currently implemented using aws provider if otherwise needs to change the provider configurations
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.
There is no single definition of what an enterprise platform is nor what enterprise bootstrapping for a platform is. However, we have been running Weave Gitops Enterprise in 2022 which has created a body of knowledge on the limitations that enterprise customers have found while bootstrapping its platform with WGE. This RFC
looks at them and proposes a solution to allow solving what we know now allowing a degree of flexibility to
adapt to the unknowns.