Sonja Chevre ✨’s Post

It’s official, I have rejoined Dynatrace 🎉 Thank you all for the warm welcome back yesterday in the office. Funny thing: I got my old employee card back! The employee experience team keeps all the cards of former employees into a box, ready for them if/when they come back. I was really touched by this gesture 💜 Don’t hesitate to reach out for coffees, I’ll be regularly into the main Linz office.

After a wonderful time as Group Product Manager at Tyk, I've decided to move on to my next adventure. I've never worked with a team that made me feel so valued and allowed me to bring my full self to work. It's been a thrilling rollercoaster ride filled with learning and growth opportunities. Today is my last day, and I've received a beautiful card signed by many Tyklings with heartfelt messages 😿 Thank you, Tyklings! I'll always be cheering for you 💜 Now, I'm off to enjoy a work-free summer. See you all in September!

If you are using OpenAPI definitions for your APIs AND deploy APIs in an automated way (CI/CD or GitOps) - where do you store your OpenAPI definitions? In the source code, in a dedicated repository or in both repositories synchronised automatically? #apiops #openapi #apideployment

For any open source software you are using and not paying for, try to imagine what would happen if: ➡ if it was no longer maintained and would no longer evolve ➡ a critical security fix was needed urgently ➡ they had anonymous maintainers if this scares you, that's a sign you should be paying for it.

I have just finished reading from Emily Omier ebook "positioning free open source software". How do you know that you have a positioning problems with your open source project? "𝘐𝘧 𝘺𝘰𝘶’𝘳𝘦 𝘤𝘰𝘮𝘮𝘦𝘳𝘤𝘪𝘢𝘭𝘪𝘻𝘪𝘯𝘨 𝘢𝘯 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦 𝘱𝘳𝘰𝘫𝘦𝘤𝘵, 𝘺𝘰𝘶 𝘴𝘩𝘰𝘶𝘭𝘥 𝘦𝘹𝘱𝘦𝘤𝘵 𝘵𝘰 𝘴𝘦𝘦 𝘳𝘦𝘭𝘢𝘵𝘪𝘷𝘦𝘭𝘺 𝘴𝘵𝘦𝘢𝘥𝘺 𝘨𝘳𝘰𝘸𝘵𝘩 𝘪𝘯 𝘣𝘰𝘵𝘩 𝘺𝘰𝘶𝘳 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦 𝘢𝘯𝘥 𝘤𝘰𝘮𝘮𝘦𝘳𝘤𝘪𝘢𝘭 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨(𝘴), 𝘦𝘴𝘱𝘦𝘤𝘪𝘢𝘭𝘭𝘺 𝘪𝘧 𝘺𝘰𝘶 𝘢𝘳𝘦 𝘪𝘯𝘷𝘦𝘴𝘵𝘪𝘯𝘨 𝘪𝘯 𝘣𝘰𝘵𝘩. 𝘐𝘧 𝘪𝘵 𝘧𝘦𝘦𝘭𝘴 𝘭𝘪𝘬𝘦 𝘰𝘯𝘦 𝘪𝘴 𝘨𝘳𝘰𝘸𝘪𝘯𝘨 𝘮𝘶𝘤𝘩 𝘴𝘭𝘰𝘸𝘦𝘳 𝘵𝘩𝘢𝘯 𝘵𝘩𝘦 𝘰𝘵𝘩𝘦𝘳, 𝘵𝘩𝘢𝘵 𝘤𝘰𝘶𝘭𝘥 𝘣𝘦 𝘢 𝘴𝘪𝘨𝘯 𝘰𝘧 𝘢 𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯𝘪𝘯𝘨 𝘱𝘳𝘰𝘣𝘭𝘦𝘮. 𝘙𝘦𝘭𝘢𝘵𝘦𝘥𝘭𝘺, 𝘮𝘢𝘯𝘺 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦 𝘴𝘵𝘢𝘳𝘵𝘶𝘱𝘴 𝘸𝘰𝘳𝘳𝘺 𝘵𝘩𝘢𝘵 𝘵𝘩𝘦𝘪𝘳 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦 𝘱𝘳𝘰𝘫𝘦𝘤𝘵 𝘪𝘴 𝘤𝘢𝘯𝘯𝘪𝘣𝘢𝘭𝘪𝘻𝘪𝘯𝘨 𝘵𝘩𝘦𝘪𝘳 𝘤𝘰𝘮𝘮𝘦𝘳𝘤𝘪𝘢𝘭 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨. 𝘐𝘧 𝘺𝘰𝘶 𝘸𝘰𝘳𝘳𝘺 𝘢𝘣𝘰𝘶𝘵 𝘵𝘩𝘢𝘵, 𝘪𝘵 𝘮𝘦𝘢𝘯𝘴 𝘺𝘰𝘶’𝘳𝘦 𝘯𝘰𝘵 𝘤𝘭𝘦𝘢𝘳 𝘰𝘯 𝘩𝘰𝘸 𝘺𝘰𝘶𝘳 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦 𝘢𝘯𝘥 𝘤𝘰𝘮𝘮𝘦𝘳𝘤𝘪𝘢𝘭 𝘰𝘧𝘧𝘦𝘳𝘪𝘯𝘨𝘴 𝘢𝘳𝘦 𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯𝘦𝘥 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵𝘭𝘺, 𝘸𝘪𝘵𝘩 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘵𝘢𝘳𝘨𝘦𝘵 𝘮𝘢𝘳𝘬𝘦𝘵𝘴 𝘢𝘯𝘥 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘷𝘢𝘭𝘶𝘦 𝘱𝘳𝘰𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯𝘴." 💎 recommended read if you want to understand (and fix) your positioning 💎

You can tell that the cloud native world is becoming more mature. And more product focused. At KubeCon in Paris last week, most talks (except maybe the ones about AI 😆) weren't just about showcasing cool techs and tools. Instead, they were about the importance of thinking about different types of users when building platforms or products. One interesting example in that regards is the Kubernetes Gateway API that enables a separation of concerns for 3 different personas: Infrastructure Providers, Cluster Operators and Application Developers. 𝘗𝘪𝘤𝘵𝘶𝘳𝘦𝘴 𝘧𝘳𝘰𝘮 𝘵𝘩𝘦 𝘵𝘢𝘭𝘬 "𝘞𝘩𝘺 𝘒𝘶𝘣𝘦𝘳𝘯𝘦𝘵𝘦𝘴 𝘐𝘴 𝘐𝘯𝘢𝘱𝘱𝘳𝘰𝘱𝘳𝘪𝘢𝘵𝘦 𝘧𝘰𝘳 𝘗𝘭𝘢𝘵𝘧𝘰𝘳𝘮𝘴, 𝘢𝘯𝘥 𝘏𝘰𝘸 𝘵𝘰 𝘔𝘢𝘬𝘦 𝘐𝘵 𝘉𝘦𝘵𝘵𝘦𝘳. - 𝘚𝘵𝘦𝘧𝘢𝘯 𝘚𝘤𝘩𝘪𝘮𝘢𝘯𝘴𝘬𝘪, 𝘜𝘱𝘣𝘰𝘶𝘯𝘥; 𝘔𝘢𝘯𝘨𝘪𝘳𝘥𝘢𝘴 𝘑𝘶𝘥𝘦𝘪𝘬𝘪𝘴, 𝘊𝘢𝘴𝘵 𝘈𝘐; 𝘚𝘦𝘣𝘢𝘴𝘵𝘪𝘢𝘯 𝘚𝘤𝘩𝘦𝘦𝘭𝘦, 𝘒𝘶𝘣𝘦𝘳𝘮𝘢𝘵𝘪𝘤" 𝘢𝘯𝘥 𝘧𝘳𝘰𝘮 𝘒𝘶𝘣𝘦𝘳𝘯𝘦𝘵𝘦𝘴 𝘎𝘢𝘵𝘦𝘸𝘢𝘺 𝘈𝘗𝘐 𝘥𝘰𝘤.

What is the difference between Kubernetes Gateway API and OpenAPI specification? Here's a helpful overview. My take on this: it makes sense to use the OpenAPI Specification (OAS) as a source of truth for configuring API routes and policies. And use tooling or scripts to parse the OAS document and generate configurations for your Gateway API. What do you think? #openstandards #gatewayapi #openapi