canonical/istio-operators

`ingress-auth` relation does not work for cross-model relations, needs `namespace` property in schema

Open

#48 opened on Jan 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

When creating the ingress-auth EnvoyFilter, istio-pilot [renders](https://github.com/canonical/istio-operators/blob/110ef7d1f1342a912e5c8e81e3dafffb4acd5da6/charms/istio-pilot/src/charm.py#L165 self.model.name) as the namespace for the auth service in this template. This only works if the ingress-auth service is in the same namespace as istio-pilot.

To fix, the ingress-auth schema will need to be updated to include a namespace property (similar to the ingress schema). Not sure if there's more to fix or tests that should be added to confirm things work.

Contributor guide

Research direction
Update the ingress auth schema to include a namespace property, similar to the ingress schema, and ensure cross model relations work by testing with services in different namespaces.
Tech stack
pythonkubernetes
Domain
backendinfrastructureclouddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Mostly clear
Prerequisites
KubernetesIstioPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60