canonical/istio-operators

istio-pilot should look for signs of another istio install during deployment

Open

#104 opened on Aug 4, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (19 forks)auto 404
enhancementgood first issue

Repository metrics

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

Description

Since istio is a global application, we often hit trouble if a charm is deployed somewhere that has:

  • another istio already running
  • a previous istio install that has been incompletely removed (possibly leaving the admission and mutating webhooks, for example)

At charm deployment (or maybe start?), we should look for these signs and block/alert the user. Maybe we'd need an action that can override this state just in case it is a false positive, but in general giving the user this info would be helpful. maybe it would be enough to debug-log things, but that feels pretty silent, especially since these leftovers usually break the istio deployment anyway so the user will be blocked one way or another.

Contributor guide