-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BLUEPRINT]Replace gitlab-ci-cd
with an example that shows self-hosted GitLab on EKS
#493
Labels
Comments
askulkarni2
changed the title
Replace
[BLUEPRINT]Replace Jun 20, 2022
gitlab-ci-cd
with an example that shows self-hosted GitLab on EKSgitlab-ci-cd
with an example that shows self-hosted GitLab on EKS
This was referenced Oct 29, 2022
@bryantbiggs @askulkarni2 I've made PR which I'm hoping at least partially resolves this issue. I thought I'd raise it before I get stuck into a Fargate example. I don't have a lot of familiarity with Fargate. I also wanted to check that this is the kind of thing you were thinking. |
@bryantbiggs @askulkarni2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the solution you'd like
The current example is not useful from a blueprint perspective - it currently appears to show how to use Terraform with GitLab as the backend which is more of a Terraform/GitLab concern than EKS/Blueprint concern. Instead, it would be more useful for users to see how they can use EKS Blueprints to run self-hosted GitLab runners on EKS using either an EC2 based route (EKS Managed node groups) or serverless route (Fargate profiles)
The text was updated successfully, but these errors were encountered: