<blockquote>
<p>Since we go through the entire microservice spin-up process manually each time a new pod comes through, we're looking to automate as much of this as possible.</p>
</blockquote>
<p>This is typically what a <em>Platform Team</em> does. Its good to provide a <em>&quot;Self Serve Portal&quot;</em> - e.g. so that developers can just intiate these things themself - whenever they have a need for it.</p>
<p>A project that tries to be an open source &quot;<em>developer portal</em>&quot; is <a href="https://backstage.io/" rel="nofollow noreferrer">Backstage</a>, created by Spotify. Even if you don't choose to use Backstage, it can serve as inspiration. See e.g. <a href="https://www.youtube.com/watch?v=3FR0G0XRDMA" rel="nofollow noreferrer">Backstage: Spotify's platform developer experience</a></p>

CC BY-SA 4.0
2021-08-11T18:32:04.470Z
2021-08-11T18:32:04.470Z
Jonas
<p>I'm currently part of a team that trains multiple pods of new hires. Each pod creates a client simulated project that involves the following steps:</p>
<ol>
<li>Creating kubernetes namespaces for each pod for deployment</li>
<li>Using spring initializer to create a Java project for each microservice (each pod's project has the same dependencies/configs but the only difference is each pod has a different name)</li>
<li>Initializing each project in GitLab with repositories for each microservice</li>
<li>Setting up webhooks for Jenkins integration (adding a Jenkinsfile, Dockerfile, gradle.properties and build.gradle with the appropriate project K8 namespace)</li>
</ol>
<p>Since we go through the entire microservice spin-up process manually each time a new pod comes through, we're looking to automate as much of this as possible.</p>
<p>Right now our approach is to create scripts that will automate kubernetes namespace creation and customization for the Dockerfile and build.gradle. However, does anyone have experience working with the GitLab API to automate webhook configuration and Jenkins pipeline config? Any advice is welcome!</p>

CC BY-SA 4.0
2021-08-13T00:10:45.057Z
I don’t know GitLab, so I can’t help you.  But your question is confusing because you use the term “Pods”, which is a Kubernetes term. If you don’t mean the Kubernetes type of pod then I would suggest you use a different term.  (Like “group”)
Vaccano
<docker><jenkins><kubernetes><gitlab><microservices>
Automating deployment of microservices from start to finish
hmnov
# Automating deployment of microservices from start to finish

(Asked by: username_0 on 2021-08-10)

I'm currently part of a team that trains multiple pods of new hires. Each pod creates a client simulated project that involves the following steps:

1. Creating kubernetes namespaces for each pod for deployment
2. Using spring initializer to create a Java project for each microservice (each pod's project has the same dependencies/configs but the only difference is each pod has a different name)
3. Initializing each project in GitLab with repositories for each microservice
4. Setting up webhooks for Jenkins integration (adding a Jenkinsfile, Dockerfile, gradle.properties and build.gradle with the appropriate project K8 namespace)

Since we go through the entire microservice spin-up process manually each time a new pod comes through, we're looking to automate as much of this as possible.

Right now our approach is to create scripts that will automate kubernetes namespace creation and customization for the Dockerfile and build.gradle. However, does anyone have experience working with the GitLab API to automate webhook configuration and Jenkins pipeline config? Any advice is welcome!

**Tags:** docker, jenkins, kubernetes, gitlab, microservices

> **Comments:**
> **username_1**: I don’t know GitLab, so I can’t help you.  But your question is confusing because you use the term “Pods”, which is a Kubernetes term. If you don’t mean the Kubernetes type of pod then I would suggest you use a different term.  (Like “group”)  

---

## 1 answers

### Answer by username_2 on 2021-08-11. Score: 1

> Since we go through the entire microservice spin-up process manually each time a new pod comes through, we're looking to automate as much of this as possible.

This is typically what a *Platform Team* does. Its good to provide a *"Self Serve Portal"* - e.g. so that developers can just intiate these things themself - whenever they have a need for it.

A project that tries to be an open source "*developer portal*" is [Backstage](https://backstage.io/), created by Spotify. Even if you don't choose to use Backstage, it can serve as inspiration. See e.g. [Backstage: Spotify's platform developer experience](https://www.youtube.com/watch?v=3FR0G0XRDMA)


---

