You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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#52openshift-service-mesh#143Fixesopenshift-service-mesh#141
// TODO: CRD proposal states "If no ingress is specified, it means the controller supports only single network topology". However, some config, such as gateway/port config, seems to be required.
63
+
// Config specifying ingress type and ingress gateway config
64
+
// +kubebuilder:validation:Required
65
+
IngressConfigIngressConfig`json:"ingress"`
66
+
67
+
// Selects the K8s Services to export to all remote meshes.
68
+
// An empty export object matches all Services in all namespaces.
69
+
// A null export rules object matches no Services.
70
+
// +kubebuilder:validation:Optional
71
+
ExportRules*ExportRules`json:"export,omitempty"`
72
+
}
73
+
74
+
// MeshFederationStatus defines the observed state of MeshFederation.
75
+
typeMeshFederationStatusstruct {
76
+
// Conditions describes the state of the MeshFederation resource.
0 commit comments