Skip to main content

Frequently asked questions

We have two Argo CD, one for production and one for the rest. Two sources?​

No, one. Connect each Argo CD in Administration › Company connections, choose argocd once in the Deployments settings: Astrolabe looks in all of them.

Why does the Deployments card on my dashboard say "Nothing here yet"?​

Because no pipeline has reported a deployment for a component of the catalog yet. The card says it word for word: "No deployment is recorded yet for a component of the catalog." Report deployments from your pipelines, see Report deployments from your pipelines, then click Refresh in the card menu.

Why does a component say "Nothing deployed yet"?​

Because no pipeline has reported a deployment under the name of this component. The name is the metadata.name of its catalog-info.yaml: see Report deployments from your pipelines. With Argo CD, the card says what is missing, with the label to add: see Common problems with Deployments.

Do I type the list of environments somewhere?​

No. The environments are the values of the label you named in Environment label (environment by default), as they are written on your Argo CD applications.

An application has no environment label. What happens?​

Astrolabe does not know which column it belongs to, so the Deployments card of the component says it: The Argo CD application shop-pay-recette belongs to shop-pay but appears in no environment. In Argo CD, add the label environment to this application, …. Add the label and the application appears: see Common problems with Deployments.

A component has no application on an environment.​

Its cell shows a dash (—).

Is argocd/app-name enough?​

No: it shows the Argo CD tab of the component. For Deployments, label your Argo CD applications: see Read the versions in Argo CD.

Do I have to write something in the catalog-info.yaml of each component?​

No. The Component label setting links a component to every Argo CD application that carries this label with its name: see Read the versions in Argo CD.

Who sees the deployments?​

Anyone who can open the component. Astrolabe reads Argo CD with the token of the integration, the same for everyone.

Does the order matter between the Argo CD integration and the Deployments settings?​

No. Either one first.

Which version is shown when an application runs several images?​

The image named after the component (.../shop-api:2.5.0 for shop-api). Without one, the image of the application's Deployment or StatefulSet.

Can someone report a deployment from their own session?​

No. Only the pipeline token reports a deployment: see Report deployments from your pipelines.

Each team has its CI. One token per team?​

No, one token for the whole Astrolabe: every CI stores the same in its ASTROLABE_PIPELINE_TOKEN secret. Replacing it means giving the new one to every CI.