Closed jewertow closed 1 day ago
For simplicity, we will not implement our CRDs, e.g. MeshPeer, Exported/ImportedServiceSet in first versions of the federation controller. Instead, we will pass these configs as an argument to the federation-controller container, like below:
MeshPeer
Exported/ImportedServiceSet
spec: containers: - name: federation-controller args: - "--meshPeers" - | - spec: remote: addresses: - lb-1234567890.us-east-1.elb.amazonaws.com - 192.168.10.56 ports: dataPlane: 15443 discovery: 15020 - "--exportedServiceSet" - | rules: - type: LabelSelector labelSelectors: - matchLabels: export-service: "true" - matchExpressions: {} - "--importedServiceSet" - | rules: - type: LabelSelector labelSelectors: - matchLabels: export-service: "true" - matchExpressions: {}
These configs should be parsed into an exported Go structure located in internal/pkg/config and then used by other components.
internal/pkg/config
i try to take this one
Done in #6
For simplicity, we will not implement our CRDs, e.g.
MeshPeer
,Exported/ImportedServiceSet
in first versions of the federation controller. Instead, we will pass these configs as an argument to the federation-controller container, like below:These configs should be parsed into an exported Go structure located in
internal/pkg/config
and then used by other components.