rootProject.name = 'service-injection'...

webhooks:
- admissionReviewVersions:
  - v1beta1
  clientConfig:
    service:
      name: fake
      namespace: istio-system
  name: sidecar-injector.istio.io
  namespaceSelector:
    matchLabels:
      istio-injection: enabled
---
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  name: istio-sidecar-injector-overlap
webhooks:
- admissionReviewVersions:
  - v1beta1
  clientConfig:

rootProject.name = 'automatic-classpath-injection-custom-test-sourceset'...

# Injected namespace.
apiVersion: v1
kind: Namespace
metadata:
  name: injected
  labels:
    istio-injection: enabled
---
# Non-injected namespace.
apiVersion: v1
kind: Namespace
metadata:
  name: non-injected
---
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
metadata:
  name: istio-sidecar-injector
webhooks:
  - admissionReviewVersions:
      - v1beta1
    clientConfig:

apiVersion: v1
kind: Namespace
metadata:
  name: bookinfo
  labels:
    istio-injection: "enabled"
spec: {}
---
apiVersion: v1
kind: Namespace
metadata:
  name: bookinfo2
  labels:
    istio-injection: "enabled"
spec: {}
---
# Deployment should not generate a warning: although two services using that deployment
# using the same port, they are in different namespaces.
apiVersion: apps/v1
kind: Deployment
metadata:

It achieves something somewhat similar to what can be done with Flask-apispec.

It has an integrated dependency injection system, inspired by Angular 2. It requires pre-registering the "injectables" (like all the other dependency injection systems I know), so, it adds to the verbosity and code repetition.

1. Start the httpbin service inside the Istio service mesh:

    If you have [automatic sidecar injection](https://istio.io/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection) enabled:

    ```bash
    kubectl apply -f httpbin.yaml
    ```

    Otherwise, manually inject the sidecars before applying:

    ```bash

    <artifactId>maven-api</artifactId>
    <version>4.0.0-beta-4-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-di</artifactId>
  <name>Maven 4 API :: Dependency Injection</name>
  <description>Maven 4 API - Dependency Injection</description>

// * originalPod: the pod before injection. If needed, we will apply some configurations from this pod on top of the final pod
// * templatePod: the rendered injection template. This is needed only to see what containers we injected
// * finalPod: the current result of injection, roughly equivalent to the merging of originalPod and templatePod

<project>
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>lifecycle-participant-reactor-dependency-injection</groupId>
    <artifactId>parent</artifactId>
    <version>1.0</version>
  </parent>

  <artifactId>module-a</artifactId>