Skip to content
This repository was archived by the owner on Jul 31, 2024. It is now read-only.

Commit 14c8efb

Browse files
author
Dennis Wendland
committed
Remove argocd
1 parent a1e12e6 commit 14c8efb

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+4
-1854
lines changed

.github/dependabot.yml

Lines changed: 0 additions & 70 deletions
This file was deleted.

.github/workflows/deploy.yaml

Lines changed: 0 additions & 81 deletions
This file was deleted.

README.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -17,23 +17,9 @@ FIWARE [data-space-connector repository](https://github.com/FIWARE/data-space-co
1717
The FIWARE Data Space Connector provides a local deployment of a Minimal Viable Dataspace.
1818
Find a detailed documentation here: [Local Deployment](./doc/LOCAL.MD)
1919

20-
### Deployment with ArgoCD
21-
22-
The FIWARE Data Space Connector is a [Helm](https://helm.sh) chart using a gitops-approach, following
23-
the [app-of-apps pattern](https://argo-cd.readthedocs.io/en/stable/operator-manual/cluster-bootstrapping), with [ArgoCD](https://argo-cd.readthedocs.io/en/stable/).
24-
25-
This repository already provides a [deployment Github action](.github/workflows/deploy.yaml) compatible with OpenShift clusters, performing deployments out of
26-
a branch created in the format `deploy/<TARGET_NAMESPACE>` and pulling the `values.yaml` from a specified gitops repository. It also requires to set the
27-
following ENVs for the Github action, `OPENSHIFT_SERVER` and `OPENSHIFT_TOKEN`, specifying the OpenShift target URL and access token, respectively.
28-
For deployment, simply fork this repository, adapt the configuration of the action to your setup and set the necessary ENVs. After creating a
29-
`deploy/<TARGET_NAMESPACE>` branch, it will perform the deployment to the specified namespace.
30-
31-
For a different cluster flavor, the GitHub action needs to be modified before to be compatible.
32-
33-
3420
### Deployment with Helm
3521

36-
Even though a gitops-approach, following the app-of-apps pattern, with ArgoCD, is the preferred way to deploy the Data-Space-Connector, not everyone has it available. Therefore, the Data-Space-Connector is also provided as an [Umbrella-Chart](https://helm.sh/docs/howto/charts_tips_and_tricks/#complex-charts-with-many-dependencies), containing all the sub-charts and their dependencies.
22+
The Data-Space-Connector is a [Helm Umbrella-Chart](https://helm.sh/docs/howto/charts_tips_and_tricks/#complex-charts-with-many-dependencies), containing all the sub-charts of the different components and their dependencies.
3723

3824
The chart is available at the repository ```https://fiware-ops.github.io/data-space-connector/```. You can install it via:
3925

@@ -48,7 +34,7 @@ The chart is available at the repository ```https://fiware-ops.github.io/data-sp
4834
structure and type of the required VCs, internal hostnames of the different connector components and providing the configuration of the DID and keys/certs.
4935
Also have a look at the [examples](#examples).
5036

51-
Configurations for all sub-charts (and sub-dependencies) can be managed through the top-level [values.yaml](./charts/data-space-connector/values.yaml) of the chart. It contains the default values of each [application](./argocd/applications/) and additional parameter shared between the components. The configuration of the applications can be changed under the key ```<APPLICATION_NAME>```, please see the individual applications and there sub-charts for the available options.
37+
Configurations for all sub-charts (and sub-dependencies) can be managed through the top-level [values.yaml](./charts/data-space-connector/values.yaml) of the chart. It contains the default values of each component and additional parameter shared between the components. The configuration of the applications can be changed under the key ```<APPLICATION_NAME>```, please see the individual applications and there sub-charts for the available options.
5238
Example:
5339
In order to change the image-tag of [Keycloak](./argocd/applications/keycloak/), the values.yaml looks as following:
5440
```yaml

argocd/applications/activation-service/Chart.yaml

Lines changed: 0 additions & 12 deletions
This file was deleted.

argocd/applications/activation-service/values.yaml

Lines changed: 0 additions & 92 deletions
This file was deleted.

argocd/applications/contract-management/Chart.yaml

Lines changed: 0 additions & 12 deletions
This file was deleted.

argocd/applications/contract-management/values.yaml

Lines changed: 0 additions & 45 deletions
This file was deleted.

argocd/applications/credentials-config-service/Chart.yaml

Lines changed: 0 additions & 12 deletions
This file was deleted.

argocd/applications/credentials-config-service/values.yaml

Lines changed: 0 additions & 17 deletions
This file was deleted.

argocd/applications/dsba-pdp/Chart.yaml

Lines changed: 0 additions & 12 deletions
This file was deleted.

0 commit comments

Comments
 (0)