Skip to content

Commit 8b2f2ed

Browse files
add callout for bootstrap existing cluster setup
1 parent db61f5b commit 8b2f2ed

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

pages/deployments/existing-cluster.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,13 @@ For users that just want to use our CD capabilities and full control of their ku
1616

1717
You are free to customize these at your own risk, usually it's not that challenging. The most likely potential gotcha is ensuring the connection stickiness configuration handles a migration to a different ingress controller from ingress-nginx.
1818

19+
{% callout severity="info" %}
20+
If you're unfamiliar with how to set up these components for your cloud, we have a number of useful example terraform setups at https://github.com/pluralsh/bootstrap/tree/main/existing.
21+
22+
It will walk you through effectively everything needed below
23+
{% /callout %}
24+
25+
1926
## Bootstrapping
2027

2128
Make sure your kubeconfig is pointing to the management cluster you want to deploy to, then run the following:

0 commit comments

Comments
 (0)