Skip to content
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.

Sign up for GitHub

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

FAQ: Shared resources #389

Merged
merged 4 commits into from
Jan 13, 2020
Merged

FAQ: Shared resources #389

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1d5a91c
add use kubectl with RBAC to FAQ
drnickiw Feb 11, 2019
d08f0f5
add FAQ where to host shared resources
drnickiw Feb 18, 2019
9b430b9
remove use kubectl file
drnickiw Feb 19, 2019
e06e6b3
Update where-host-shared-resources.md
osterman Jan 13, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions content/faq/where-host-shared-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Where should we host shared resources?"
description: "We recommend deploying a dedicated cluster in a separate account for shared platform services."
tags:
- shared resources
- shared platform services
- Codefresh
- Jira
- CRM
- corp
---

## Question

Is there a recommendation for where we should host shared resources like Keycloak, Jenkins or Teleport?

## Answer

We typically recommend to our customers that we provision a dedicated Kubernetes cluster a separate account for shared platform services. This is a good place to host internally facing services like Codefresh Enterprise, Jira, CRMs, etc. This is what we typlically call the "corp" account (and cluster).