SShortSingh.
Back to feed

Making My Platform API Reconcile Application Updates

0
·27 views

In the previous post, I built the first real behavior for Platform Lab. A developer could create: apiVersion: platform.shubforge.dev/v1alpha1 kind: Application metadata: name: greeting-service spec: image: greeting-service:1.0.0 replicas: 1 port: containerPort: 8080 and the Platform Operator would create: Application | v Platform Operator | +------ Deployment | +------ Service That was the first point where the Application API actually resulted in real Kubernetes resources. But there was another important question. What happens when the Application changes? Creating resources once is useful, b

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Entitlements Are a Domain, Not a Feature Flag

It usually starts with one feature. The product team wants the new reporting dashboard available only on the enterprise plan, and there's no plan model in the code yet. The flag service is already wired in and supports targeting, and a segment called enterprise-customers takes ten minutes to set up. A year later there are a dozen such segments. Every grant now goes through engineering, the code understands plans only as segment names, billing and access drift apart, and change logs are not sufficient to audit the proper state of customer product access.