Export by matching labels #143

bartoszmajsak · 2025-01-20T16:50:15Z

Introduce support for service selectors that allow users to export specific services based on labels across any namespace.

The implementation should support matchLabels criteria, with key:value pairs.

Example structure

serviceSelectors:
  - matchLabels:
      export: "true"

The text was updated successfully, but these errors were encountered:

This PR extends `MeshFederation` Custom Resource with configuration for local Federation setup. This configuration that includes: - network name - trust domain - controlPlane's namespace - required to create certain mesh-wide resources - ingress configuration to be used for creating Federation Ingress Gateway - the default should be `istio` - support for `openshift-router` It also defines export rules based on selectors (both label matching as well as expressions) ### Current assumptions - there should be only one instance of `MeshFederation` per namespace - `metadata.name` is used instead of originally proposed `id` to uniquely identify the local instance ### Related Issues API for openshift-service-mesh#52 openshift-service-mesh#143 Fixes openshift-service-mesh#141

This PR extends `MeshFederation` Custom Resource with configuration for local Federation setup. This configuration that includes: - network name - trust domain - controlPlane's namespace - required to create certain mesh-wide resources - ingress configuration to be used for creating Federation Ingress Gateway - the default should be `istio` - support for `openshift-router` It also defines export rules based on selectors (both label matching as well as expressions) ### Current assumptions - there should be only one instance of `MeshFederation` per namespace - `metadata.name` is used instead of originally proposed `id` to uniquely identify the local instance ### Related Issues API for #52 #143 Fixes #141

This PR extends `MeshFederation` Custom Resource with configuration for local Federation setup. This configuration includes: - network name - trust domain - controlPlane's namespace - required to create certain mesh-wide resources - ingress configuration to be used for creating Federation Ingress Gateway - the default should be `istio` - support for `openshift-router` It also defines export rules based on selectors (both label matching as well as expressions) ### Current assumptions - there should be only one instance of `MeshFederation` per namespace - `metadata.name` is used instead of originally proposed `id` to uniquely identify the local instance ### Related Issues API for #52 #143 Fixes #141 Co-authored-by: Eoin Fennessy <[email protected]>

This commit introduces the initial implementation of the MeshFederation controller. The controller is responsible for: - Managing the MeshFederation server lifecycle (openshift-service-mesh#152) - Configuring MeshFederation resources, including: - IngressGateway - PeerAuthentication - EnvoyFilter (for OpenShift Router) - Routes (for OpenShift Router) - Watching Kubernetes services to: - Push SotW updates to all connected peers (openshift-service-mesh#153) - Update MeshFederation cluster configuration - Support both label selectors and expressions (openshift-service-mesh#52 openshift-service-mesh#143) Basic EnvTest tests are included to verify the setup. Fixes openshift-service-mesh#152 openshift-service-mesh#52 openshift-service-mesh#143 openshift-service-mesh#153

This commit introduces the initial implementation of the MeshFederation controller. The controller is responsible for: - Managing the MeshFederation server lifecycle (openshift-service-mesh#152) - removes a need for a channel to trigger push - pushing directly instead - Configuring MeshFederation resources, including: - IngressGateway - PeerAuthentication - EnvoyFilter (for OpenShift Router) - Routes (for OpenShift Router) - Watching Kubernetes services to: - Push SotW updates to all connected peers (openshift-service-mesh#153) - Update MeshFederation cluster configuration - Support both label selectors and expressions (openshift-service-mesh#52 openshift-service-mesh#143) Basic EnvTest tests are included to verify the setup. Fixes openshift-service-mesh#152 openshift-service-mesh#52 openshift-service-mesh#143 openshift-service-mesh#153

bartoszmajsak changed the title ~~Exporting by Labels~~ Exporting by matching labels Jan 20, 2025

bartoszmajsak changed the title ~~Exporting by matching labels~~ Export by matching labels Jan 20, 2025

bartoszmajsak mentioned this issue Jan 20, 2025

Import Rules #151

Open

bartoszmajsak mentioned this issue Jan 24, 2025

feat(api): introduces MeshFederation API #166

Merged

bartoszmajsak linked a pull request Jan 27, 2025 that will close this issue

feat(ctrl): implements MeshFederation reconciliation #170

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Export by matching labels #143

Export by matching labels #143

bartoszmajsak commented Jan 20, 2025

Export by matching labels #143

Export by matching labels #143

Comments

bartoszmajsak commented Jan 20, 2025

Example structure