After GitOps configuration is created, you do not need to do anything to deploy the DIP or CNF intents. All the intent realization are performed by TCA automatically. Do expect a delay of a few minutes, because TCA pulls the intents periodically.
DIP Intents
You can monitor the status of DIP intents in TCA manager UI by going to the page. The DIP instance displays the name, version, status as well as the cluster that it is applied to. You can also see the DIP intent (Node Customisation) applied on the Node pools by navigating to under the specified Node pool.
Clicking the >> will display the detailed view, which contains the actual node customization that matches what users specify in their git repository.
The Network Functions tab shows a list of CNFs that are dependent on this DIP intent. You can navigate to each CNF instance by clicking the hyperlinked CNF name.
If a DIP intent is invalid, the detailed view is shown with the error message on why it is invalid. You can fix the intent accordingly in your git repository.
CNF Intents
You can monitor the CNF intents by navigating to the page. The CNF instance displays the name, status, and cluster it is deployed to. If the CNF instance is dependent on a DIP, it also displays the dependent DIP name and version.
CNF instance that depends on a DIP instance will always be deployed after the dependent DIP instance is deployed successfully. TCA guarantees that this ordering is strictly enforced.
Clicking the >> will display the detailed view, which contains the data that matches the CNF intent in the git repository.
If a CNF intent is invalid, the detailed view will show the error message on why it is invalid. Users can fix the intent accordingly in their git repository.
