Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArgoCD crossplane application fails to be deployed as it uses a wrong Argocd project name #42

Closed
cmoulliard opened this issue Oct 18, 2023 · 6 comments · Fixed by #64
Closed

Comments

@cmoulliard
Copy link
Contributor

Issue

The ArgoCD crossplane application fails to be deployed as it refers to a wrong project name. Name should be: idpbuilder-local-gitserver and not idpbuilder-embedded-gitserver

Screenshot 2023-10-18 at 11 26 08

@cmoulliard cmoulliard changed the title ArgoCD crossplane application fails to be deployed ArgoCD crossplane application fails to be deployed as it uses a wrong Argocd project name Oct 18, 2023
@nimakaviani
Copy link
Contributor

nimakaviani commented Oct 25, 2023

hmmm, the default value for buildName is localdev actually and not local as seen here:

CreateCmd.PersistentFlags().StringVar(&buildName, "buildName", "localdev", "Name for build (Prefix for kind cluster name, pod names, etc)")

so, the current fix in #43 still won't work unless users explicitly pass --buildName=local.

i suggest we remove the --buildName flag from the create command and just default the buildName to local for the first release so things work as expected. Given that the idpbuilder only launches a local idp, this should work fine conceptually.

Separately though, do we see any particular value in having a configurable buildName?

@cmoulliard
Copy link
Contributor Author

Separately though, do we see any particular value in having a configurable buildName?

Such a "build name" is also used as the name to configure the kind cluster to be deleted/created. See here: https://github.com/cnoe-io/idpbuilder/blob/main/pkg/kind/cluster.go#L81 or https://github.com/cnoe-io/idpbuilder/blob/main/pkg/kind/cluster.go#L95.
So, if a user is interested to create several kind clusters, than such a name is relevant but less from the build (or IDP creation) point of view but more to have x kind clusters

@cmoulliard
Copy link
Contributor Author

As my pr has been merged, I suggest to close this issue but that we create another one or several to:

  • Rename buildName parameter to clusterName or simply name as it should be used only to name the cluster and not by example used part of the command gitserver create --buildName
  • Review how we name the namespace, image tag, etc

@nimakaviani
Copy link
Contributor

problem is the PR doesnt fix the issue unless we change the default value for --buildName to local. thats one way to go about it but things break if people set a different name. that's why I am suggesting the alternative approaches.

Also, this needs fixing before we cut a release.

@nabuskey
Copy link
Collaborator

#43 (comment)

I suggest use the default project for this release.

Rename buildName parameter to clusterName or simply name as it should be used only to name the cluster and not by example used part of the command gitserver create --buildName

I also agree with this.

@greghaynes
Copy link
Contributor

I like this idea. Build name is a leftover from when this whole thing was in ideation - it makes sense to only support one "build" per cluster as all the CRDs and many of the controllers we're installing are singleton.

This was referenced Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants