Open marceljonik opened 1 week ago
The title of your PR 'Feat: add new controlplane service' is non-compliant to the conventions. Please refer to our GitHub documentation in Notion.
The title of your PR 'Feat: add new controlplane service' is non-compliant to the conventions. Please refer to our GitHub documentation in Notion.
@holgerson97
Since status services is splitted into 2 services, the endpoints in both services currently have the same prefix. Do we need to adapt the ingress path in order for treafik being able to route in correctly?
The title of your PR 'Feat: add new controlplane service' is non-compliant to the conventions. Please refer to our GitHub documentation in Notion.
The title of your PR 'Feat: add new controlplane service' is non-compliant to the conventions. Please refer to our GitHub documentation in Notion.
@holgerson97
Since status services is splitted into 2 services, the endpoints in both services currently have the same prefix. Do we need to adapt the ingress path in order for treafik being able to route in correctly?
Adding up on this I tried my best regarding the needed changes. It would be amazing though If you can check and help me with potential missing things since I'm not super deep into the topic yet.
Summary
Description
Adjusting charts to changes due to the restructuring of controlplane. This includes removing the gateway, adding a new services and deleting some not needed credentials.
Related Issue
57
Motivation and Context
Needed to fullfil the restructuring.
How Has This Been Tested?
Not tested yet.