Merge pull request 'chore(deps): update ghcr.io/renovatebot/renovate docker tag to v39.254.3' (#10) from renovate/ghcr.io-renovatebot-renovate-39.x into main

Reviewed-on: #10

.gitea/workflows/renovate.yaml

@@ -10,7 +10,7 @@ on:
 jobs:
   renovate:
     runs-on: ubuntu-latest
-    container: ghcr.io/renovatebot/renovate:39.207.2
+    container: ghcr.io/renovatebot/renovate:39.254.3
     steps:
       - uses: actions/checkout@v4
       - run: renovate

config.toml

@@ -101,10 +101,10 @@ stylesheets = []
 # Remote repository for your Zola site.
 # Used for `show_remote_changes` and `show_remote_source` (see below).
 # Supports GitHub, GitLab, Gitea, and Codeberg.
-remote_repository_url = "https://github.com/alexohneander/alexohneander-zola"
+remote_repository_url = "https://git.dev-null.rocks/alexohneander/alexohneander-zola"
 # Set this to "auto" to try and auto-detect the platform based on the repository URL.
 # Accepted values are "github", "gitlab", "gitea", and "codeberg".
-remote_repository_git_platform = "auto"  # Defaults to "auto".
+remote_repository_git_platform = "gitea"  # Defaults to "auto".
 # Branch in the repo hosting the Zola site.
 remote_repository_branch = "main"  # Defaults to "main".
 # Show a link to the commit history of updated posts, right next to the last updated date.

content/blog/use-real-servers-again/index.md

@@ -0,0 +1,30 @@
++++
+title = "Use real Servers again"
+date = 2025-03-18
+updated = 2025-03-18
+description = "Is the cloud really the ultimate solution? This post questions the current cloud-first mentality, arguing for a return to 'real' servers and discussing the hidden costs, dependency, and political vulnerabilities of relying solely on the cloud."
+
+[taxonomies]
+tags = ["baremetal", "cloud", "google", "aws", "cloud"]
+
+[extra]
+toc = false
+pinned = true
+quick_navigation_buttons = true
++++
+
+![Private Cluster](https://preview.redd.it/k3pj0bjpr7s61.jpg?width=1080&crop=smart&auto=webp&s=8f1cee3bfc17c36c165e9e7dd7d5fafda6c943c6)
+
+## The Case for Bringing Back "Real" Servers: Why the Cloud Isn't Always King
+
+For years now, the narrative has been clear: the cloud is the future. Businesses big and small have flocked to platforms like Google Cloud and AWS, lured by promises of scalability, flexibility, and cost savings. But lately, I've been thinking: is this headlong rush to the cloud truly the best path? I believe it's time we seriously consider a return to "real" servers and acknowledge the limitations and potential pitfalls of relying solely on these tech giants.
+
+Let's be honest, the cloud providers aren't doing anything magical. At their core, Google, Amazon, and the rest are simply running massive data centers filled with… you guessed it… servers. They've built impressive infrastructure and offer a wide range of services on top, but fundamentally, "they also just cook with water," as the saying goes. The perceived complexity and innovation can sometimes mask the underlying reality.
+
+One of the biggest issues I've encountered, and I know many others have too, is the often-opaque pricing structure of cloud services. While the initial allure might be pay-as-you-go flexibility, the reality can be a tangled web of instance types, storage tiers, network egress fees, and a host of other charges that can quickly balloon your monthly bill. These "hidden costs" can be difficult to predict and manage, often negating the promised cost savings compared to the more predictable expenses of owning and maintaining your own hardware.
+
+Furthermore, the increasing reliance on a handful of major cloud providers creates a significant dependency. We are essentially entrusting critical data and infrastructure to these companies, making ourselves vulnerable to their pricing changes, service outages, and even their long-term strategic decisions. This lack of control is a worrying trend, especially when considering the potential for vendor lock-in, where migrating away from a specific cloud platform becomes prohibitively expensive and complex.
+
+Beyond the technical and economic considerations, the current political landscape adds another layer of risk to our cloud dependency. Imagine a scenario where political tensions rise, and a country like the United States, under a potential future administration, decides to impose tariffs on cloud services. Someone like Trump, for example, has shown a willingness to use tariffs as a political tool. If such tariffs were levied on cloud usage, businesses relying heavily on these platforms would face significant and potentially crippling cost increases. This geopolitical uncertainty makes the idea of having more control over our own infrastructure increasingly appealing.
+
+In conclusion, while the cloud offers undeniable benefits in certain situations, it's crucial to have a more balanced perspective. We need to recognize that "real" servers still hold significant value, offering greater control, potentially more predictable costs, and insulation from the unpredictable nature of both cloud pricing and international politics. It's time to re-evaluate our cloud-first mentality and consider whether bringing some workloads back in-house, or at least diversifying our infrastructure, might be a more resilient and ultimately more cost-effective strategy in the long run.

content/pages/experience/index.md

@@ -53,9 +53,19 @@ Agency for internet and design founded in 1998, established in Kastellaun in the
 
 ## Projects
 
+### DevOps Engineer, AEF AgIN Common-Connector
+
+The Common-Connector is being developed by the Agricultural Industry Electronics Foundation (AEF) as part of their Agricultural Interoperability Network (AgIN) initiative. In my role as a DevOps engineer, I supported the tender and contributed to the development of the MVP. Our team developed a Java Spring Boot application to facilitate seamless data exchange between platforms.
+
+- Conception and Development of a Dev Cluster based on AWS EKS (IaC)
+- Setting up build and deployment pipelines (GitLab)
+- Development of a test concept (Playwright, Testcontainers)
+- Development and integration of the operator pattern in a Java Spring Boot application
+- Development of the security pipelines (SonarQube, Mend, SAST)
+
 ### DevOps Engineer, Cofinity-X
 
-**since 2023**
+**until 2024**
 
 Cofinity-X is the first operator of the Catena-X network, connecting automotive partners at every level of the value chain. As a DevOps engineer, I was responsible for the enablement services.
 
@@ -84,4 +94,5 @@ Just right for your pharmacy! amamed is the only digital solution on the market
 - Provision of various services (including backend APIs, MariaDB clusters, NATs, Redis)
 - Design and operation of Kubernetes clusters (3 locations)
 - Management of automated pipelines via Bitbucket Pipelines (continuous integration)
-- IT administration for 6 individuals (SysOps)
+- IT administration for 6 individuals (SysOps)
+

deploy/deployment.yaml

@@ -17,6 +17,6 @@ spec:
     spec:
       containers:
         - name: alexohneander-zola
-          image: git.dev-null.rocks/alexohneander/alexohneander-zola:sha-c1c1512
+          image: git.dev-null.rocks/alexohneander/alexohneander-zola:0.1.4
           ports:
             - containerPort: 80

templates/partials/footer.html

@@ -8,7 +8,7 @@
     {%- set blank_target = "" -%}
 {%- endif -%}
 
-<footer>
+<footer>        
     <section>
         <nav class="socials nav-navs">
             {%- if config.extra.socials or config.extra.email %}
@@ -66,6 +66,9 @@
             {% endif %}
         </nav>
 
+        <p align="center">
+            <iframe src="https://tryhackme.com/api/v2/badges/public-profile?userPublicId=4027495" style='border:none;'></iframe>
+        </p>
         {# Footer menu #}
         <nav class="nav-navs">
             {%- if config.extra.footer_menu %}
@@ -103,8 +106,7 @@
 
                 {# Shows "Powered by Zola & tabi" notice #}
                 {{ macros_translate::translate(key="powered_by", default="Powered by", language_strings=language_strings) }}
-                <a rel="{{ rel_attributes }}" {{ blank_target }} href="https://www.getzola.org">Zola</a>
-
+                  <a rel="{{ rel_attributes }}" {{ blank_target }} href="https://www.getzola.org">Zola</a> and running on real <a {{ blank_target }} href="/blog/use-real-servers-again">Servers</a>
                 {# Shows link to remote repository #}
                 {%- if config.extra.remote_repository_url and config.extra.show_remote_source | default(value=true) -%}
                 {{ separator }}