envoyproxy/gateway

Reconcile immutable fields for `Service` objects created

Open

#1,844 opened on Aug 29, 2023

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Go (802 forks)auto 404
area/apiarea/infra-mgrhelp wantedkind/enhancement

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

Description

Description:

When changes are made to fields such as loadBalancerClass, they can only be realized by deleting and recreating the Service object.

Other operators that handle these kinds of things do so with force flag so that the user knowingly opts in to this destructive behavior.

apiVersion: config.gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  ...
spec:
  provider:
    type: Kubernetes
    kubernetes:
      ...
      envoyService:
        force: true # force reconciliation by delete/create

Related Issues:

https://github.com/envoyproxy/gateway/pull/1840 https://github.com/envoyproxy/gateway/issues/1818

Contributor guide

Research direction
Study immutable fields of Kubernetes Service objects and how other operators implement the force flag for destructive reconciliation. Look at existing PR #1840 for context.
Tech stack
gokubernetes
Domain
backendapiinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65