Merge pull request #15655 from mihai-satmarean/event/2026-sibiu

[Sibiu-2026] Add speaker page (3 speakers), legal page, program page and program for day 1.

Author: toshywoshy

assets/events/2026-sibiu/speakers/edithkarda.jpeg

@@ -0,0 +1,198 @@
++++
+Title = "Legal"
+Type = "event"
+Description = "Legal information for devopsdays sibiu 2026"
++++
+
+
+
+# Terms and Conditions & Privacy Policy
+
+> **This page contains the Terms and Conditions as well as the Privacy Policy.  
+> We kindly ask you to review them before proceeding with the ticket purchase.**
+
+---
+
+## Terms and Conditions for DevOpsDays Sibiu Ticket Purchase
+
+### 1. General information
+DevOpsDays Sibiu is a three day, community driven technology event taking place in May.
+
+- Day 1: 27 May
+- Day 2: 28 May
+- Day 3: 29 May
+
+The event brings together conference days, workshops, social experiences, and live streaming access.  
+Ticket purchase confirms acceptance of these Terms and Conditions and the associated Privacy Policy.
+
+### 2. Agreement with the Privacy Policy
+By completing a ticket purchase, each participant confirms agreement with the DevOpsDays Sibiu Privacy Policy. Personal data supports event organisation, access management, communication, and community engagement, in line with applicable data protection principles.
+
+### 3. Ticket validity and access
+Each ticket provides access to the specific day or days selected during purchase.
+
+- Conference tickets for Day 1 provide access on 27 May
+- Conference tickets for Day 2 provide access on 28 May
+- Combined tickets provide access on both Day 1 and Day 2
+- Workshop tickets provide access to Day 3 workshops on 29 May
+- After party tickets provide access to the official social event on Day 1, 27 May
+- Live streaming access provides online viewing of selected sessions
+
+Each ticket applies to one individual.
+
+### 4. Ticket pricing and sales periods
+Day 1 & 2 ticket sales follow a calendar based structure.
+
+- January early bird: 5 prize draw entries
+- February early bird: 4 prize draw entries
+- March early bird: 3 prize draw entries
+- April early bird: 2 prize draw entries
+- Tickets sold in May: 1 prize draw entry
+
+Ticket prices remain consistent across early bird phases, while the number of prize draw entries gradually decreases over time.
+
+### 5. Prize draw and raffle tickets
+Prize draws take place at the end of:
+- Day 1 – 27 May
+- Day 2 – 28 May
+
+Eligible ticket holders receive physical raffle style tickets during check in.  
+Each raffle ticket represents one entry for that specific day.
+
+- Combined tickets receive raffle tickets for each applicable day
+- Workshop tickets, after party tickets, and live streaming access include zero prize draw entries
+
+Winners must be present at the event at the time of the draw.  
+Prizes may include sponsor gifts, partner vouchers, or community rewards. Cash alternatives are not available.
+
+### 6. Student ticket refund programme
+Students benefit from a full same day refund for conference tickets when all conditions apply:
+
+- Arrival before 14:00 on the valid ticket day
+- Presentation of a valid student document and personal ID
+- Physical attendance at the event on that day
+
+The refund applies per day.  
+After party tickets are excluded.  
+All refunds are issued in cash after 14:00, not during the registration period.
+
+### 7. Cancellation and refund policy
+Refunds apply when cancellation requests reach organisers no later than fourteen calendar days before Day 1 (27 May).
+
+After this deadline, refunds are not available.  
+Ticket name changes may still be requested as described in section 11.
+
+Student refunds remain independent and are handled on site.
+
+### 8. Workshops on Day 3
+Workshop tickets grant access to hands on sessions on 29 May.
+
+- Student and non student tickets follow separate pricing
+- Participation requires prior ticket purchase
+- Attendance is first come, first served
+- No advance reservations or prebooking
+
+Workshop tickets are independent of conference day tickets.
+
+### 9. Live streaming access
+Live streaming access provides online viewing of selected sessions at zero cost.
+
+DevOpsDays Sibiu may limit or exclude sessions due to speaker requests or organisational, technical, or content related reasons.  
+Streaming availability depends on technical conditions and speaker consent.
+
+### 10. After party ticket details
+The after party takes place on Day 1, 27 May.
+
+The ticket includes:
+- Entry to the official social gathering
+- Food
+- Three drinks per person
+
+All participants follow the DevOpsDays Code of Conduct.  
+Organisers may act to ensure a safe and welcoming environment.
+
+### 11. Ticket name changes
+Ticket name changes are supported until seven calendar days before Day 1 (27 May).  
+Later requests may receive limited support.
+
+### 12. Programme evolution
+Organisers may adapt the programme, speakers, schedule, or venue when required, while preserving the overall event experience.
+
+### 13. Community standards
+All participants contribute to a respectful, inclusive, and welcoming environment in line with the DevOpsDays Code of Conduct.
+
+### 14. Contact and support
+Questions related to tickets, refunds, access, or data handling may be addressed through official DevOpsDays Sibiu communication channels.
+
+---
+
+## Privacy Policy for DevOpsDays Sibiu
+
+### 1. Purpose of this Privacy Policy
+This policy explains how DevOpsDays Sibiu collects, uses, stores, and protects personal data related to event participation.
+
+### 2. Data controller
+DevOpsDays Sibiu acts as the data controller for all personal data processed in relation to the event.
+
+### 3. Personal data collected
+Collected data may include:
+
+- Name and surname
+- Email address
+- Ticket type and attendance day
+- Student status verification
+- Workshop or prize draw participation
+- Technical data related to live streaming access
+
+### 4. Sources of personal data
+Data is collected directly from participants during ticket purchase, registration, check in, event participation, and voluntary communication.
+
+### 5. Purpose of data processing
+Personal data supports:
+
+- Event organisation and logistics
+- Ticket management and access control
+- Student refund verification
+- Prize draw administration
+- Event communication
+- Community safety and Code of Conduct enforcement
+- Statistical insights for future events
+
+### 6. Legal basis for processing
+Processing is based on one or more of the following:
+
+- Performance of a contract
+- Participant consent
+- Legitimate organisational interests
+- Legal obligations where applicable
+
+### 7. Data sharing
+Data may be shared with trusted partners (ticketing platforms, payment providers, venue systems) under strict confidentiality and purpose limitation.
+
+### 8. Prize draws and raffles
+Personal data is never sold.  
+Raffle tickets carry no personal identifiers. Limited contact data may be required for prize fulfilment.
+
+### 9. Live streaming and recordings
+Some sessions may be recorded with speaker consent.  
+Audience members appearing incidentally accept this as part of participation.
+
+### 10. Data retention
+Data is retained only as long as necessary for operational, legal, and reporting purposes.
+
+### 11. Data security
+Appropriate technical and organisational safeguards protect personal data. Access is limited to authorised parties.
+
+### 12. Participant rights
+Participants may request access, correction, deletion, or clarification regarding their personal data.
+
+### 13. Cookies and tracking
+Event websites may use essential cookies. Platform specific cookie policies apply where relevant.
+
+### 14. Changes to this Privacy Policy
+Updates may occur to reflect legal or operational changes. The latest version remains published on official channels.
+
+### 15. Contact
+For questions related to this Privacy Policy, contact:  
+**sibiu@devopsdays.org**
+															

assets/events/2026-sibiu/speakers/joepiscaer.jpg

@@ -0,0 +1,25 @@
++++
+Title = "Program"
+Type = "program"
+Description = "Program for devopsdays sibiu 2026"
+Icons = "false"
++++
+
+<div class="column" style="margin-bottom:24px;">
+  <div class="col-lg-2 col-md-2"><b>Color Keys:</b></div>
+
+  <div class="col-lg-2 col-md-2 program-element program-talk">Talk</div>
+  <div class="col-lg-2 col-md-2 program-element program-ignite">Ignite</div>
+  <div class="col-lg-2 col-md-2 program-element program-workshop">Workshop</div>
+  <div class="col-lg-2 col-md-2 program-element program-open-space">Open Space</div>
+
+  <div class="col-lg-2 col-md-2 program-element program-keynote"
+       style="background-color:#2f7d3a; color:#fff;">
+    Keynote
+  </div>
+
+  <div class="col-lg-2 col-md-2 program-element"
+       style="background-color:#e8e8e8; color:#333;">
+    Break or other event
+  </div>
+</div>

assets/events/2026-sibiu/speakers/sutapasarkar.jpeg

@@ -0,0 +1,10 @@
++++
+Talk_date = ""
+Talk_start_time = ""
+Talk_end_time = ""
+Title = "Edith Karda - Unmasking Traefik: Multi-Domain Routing Patterns in Kubernetes"
+Type = "talk"
+Speakers = ["edith-karda"]
++++
+
+Ever wondered how Traefik manages domain magic in the background? We’ll solve the mystery of having multiple domains in one environment, how it can improve cloud platform migrations, and create a seamless user experience for end-users.  Context: Traefik Proxy as an Ingress Controller in Kubernetes.  Based on a real-world migration experience, this case study will walk you through the process of configuring not one, but three domains with a single IP!  It also improved our overall infrastructure in multiple ways, reducing resources being only one of them.  Curious about another scenario?  Find out how two domains can happily live together in a cluster, but be completely independent, each having their separate IP and microservices.  This session is perfect for anyone curious to dive into Traefik’s capabilities and discover different uses of multi-domain setups.

content/events/2026-sibiu/legal.md

@@ -0,0 +1,10 @@
++++
+Talk_date = ""
+Talk_start_time = ""
+Talk_end_time = ""
+Title = "If You Feel Behind, You’re Probably Paying Attention"
+Type = "talk"
+Speakers = ["joep-piscaer"]
++++
+
+Impostor syndrome is usually framed as a personal failing: a lack of confidence, a mindset problem, something you need to “work through.” But what if the problem isn't you?  You’re not inexperienced. You’re not lazy. You're not bad at your job. I realized something else was going on: no one’s real experience matches the cloud-native story we tell in public.  In the cloud-native world, operators and admins are surrounded by a constant narrative of effortless success: platforms that scale cleanly, teams that “just adopt Kubernetes,” architectures that assume infinite time, talent, and budget. Conference talks are polished. Case studies are sanitized. Failure is implied to be a 'you' problem.  Yet privately, most practitioners are struggling. Technology is complex. Platforms and systems are brittle. Toolchains are overwhelming. Upgrades are painful projects. On-call is exhausting. And almost no one’s lived experience matches what the industry claims is normal.  This talk argues that what we’re experiencing isn’t just impostor syndrome — it’s pluralistic ignorance amplified by burnout. Everyone is struggling to keep up, but no one admits it, because admitting it feels like failure. So we stay quiet. We internalize the gap. We blame ourselves. We work harder and harder, up to, and beyond our breaking point.  At Cloud Native Rejekts, I want to say the quiet part out loud and break that silence together.  This talk is for operators who keep real systems running, who are tired of pretending and who want honesty instead of hype. We’ll examine how hype amplifies self-doubt, why feeling “behind” is often a sign of realism, and how collective honesty—not more expertise—is the missing ingredient in the cloud-native ecosystem.  If you’ve ever thought “everyone else seems to have this figured out” — this talk is for you.

content/events/2026-sibiu/program.md

@@ -0,0 +1,10 @@
++++
+Talk_date = ""
+Talk_start_time = ""
+Talk_end_time = ""
+Title = "Platform Obesity, not Complexity, is killing our platforms"
+Type = "talk"
+Speakers = ["joep-piscaer"]
++++
+
+We like to say Kubernetes platforms fail because they’re “too complex”. But complexity isn’t the problem. Platforms fail because they’re obese.  They’re bloated with an excess of features, tools, abstractions, and opinions that far exceed an organization’s operational capacity and cognitive load—especially in enterprises, regulated environments, and talent-constrained teams.  The cloud-native ecosystem doesn’t help. It hands out sweets constantly: one more controller, one more abstraction, one more “best practice.” Each addition seems harmless in isolation. Saying yes is easy. Saying no is career-limiting: since no-one wants to admit their own reality doesn't match the industry narrative. The Pluralistic Ignorance is real, yo.  The ecosystem rewards addition, not subtraction. Often, “simplification” efforts often do the opposite—layering abstractions on top of abstractions until the platform is heavier, slower, and harder to operate and change than before.  Eventually, the platform collides with reality: finite talent, finite attention, finite time. Cognitive load exceeds capacity. Operational friction grows. Engineering quality cracks. Business outcomes stall. ROI quietly evaporates.  This isn’t a tooling failure. It’s a constraint failure.  So how do you fix an obese platform? The same way you fix obesity: by creating a calorie deficit, rigorous exercise and discipline. In the platform world, that means recognizing constraints and designing for and staying within those limits, across technology, processes, organizational culture, budget, engineering skills, team cognitive load and more.  Dare to play the hard 'less is more' subtraction game, not the easy game of addition: treat dealing with constraints, subtraction, prioritization and trade-offs as first-class engineering skills—not as signs of lack of ambition.

content/events/2026-sibiu/program/edith-karda.md

@@ -0,0 +1,15 @@
++++
+Talk_date = ""
+Talk_start_time = ""
+Talk_end_time = ""
+Title = "The rise of Risk Ops teams - a solution for reducing cognitive load in DevOps teams."
+Type = "talk"
+Speakers = ["sutapa-sankar"]
++++
+
+In the fast-paced realm of DevOps, integrating security early often overwhelms DevOps teams with complex alerts and mental strain. Risk Ops can reduce this cognitive load by embedding continuous risk assessments, vulnerability management, directly into development pipelines. While Security Champions help to ensure secure coding practices are followed early in the development cycle, Risk Ops teams translate technical alerts into actionable, business-contextualized insights which enable DevOps teams to focus on delivering features rather than deciphering risks. Embedding risk knowledge within DevOps teams enables the translation of risk and security challenges into actionable, developer-friendly tasks, many of which can be efficiently mitigated through automation. This collaboration fosters a “secure by design” culture where risk teams guide rather than gatekeep, work together with DevOps teams to resolve risk and security related issues , empowering DevOps teams to build resilient applications with speed, confidence, and reduced friction.
+During this talk, I will share firsthand experiences where my team has developed structural solutions to security and risk challenges, helping embed regulatory compliance requirements such as DORA, GDPR etc. into DevOps workflows. If you're a developer, tester, or architect eager to see how risk ops teams can help you remove cognitive load from your DevOps teams, then this session is for you.
+Key Takeaways:
+
+1. Learn about Risk Ops and how they help to alleviate cognitive load within DevOps teams.
+2. Learn about tips and tricks to embedding Risk Ops within your delivery teams for faster delivery.

content/events/2026-sibiu/program/joep-piscaer-1.md

@@ -0,0 +1,5 @@
++++
+Title = "Speakers"
+Type = "speakers"
+Description = "Speakers for devopsdays sibiu 2026"
++++