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

use localtest.me suffix to resolve localhost #29

Merged
merged 1 commit into from
Oct 18, 2023
Merged

Conversation

jessesanford
Copy link
Contributor

No description provided.

@jessesanford jessesanford requested a review from nabuskey October 16, 2023 20:18
@nimakaviani nimakaviani self-requested a review October 16, 2023 20:47
Copy link
Contributor

@nimakaviani nimakaviani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few more occurences of the same domain name that we should also fix

pkg/controllers/localbuild/controller.go
27:     gitServerIngressHostnameBase     string = ".idpbuilder.cnoe.io.local"

pkg/controllers/gitserver/controller.go
26:     gitServerIngressHostnameBase     string = ".idpbuilder.cnoe.io.local"

pkg/apps/srv/argocd/ingress.yaml
13:  - host: argocd.idpbuilder.cnoe.io.local

@jessesanford
Copy link
Contributor Author

There are a few more occurences of the same domain name that we should also fix

pkg/controllers/localbuild/controller.go
27:     gitServerIngressHostnameBase     string = ".idpbuilder.cnoe.io.local"

pkg/controllers/gitserver/controller.go
26:     gitServerIngressHostnameBase     string = ".idpbuilder.cnoe.io.local"

pkg/apps/srv/argocd/ingress.yaml
13:  - host: argocd.idpbuilder.cnoe.io.local

These are used internally so are using the automatically generated service hostnames. We do need to figure out that duplication though. I will create a separate issue for that.


Backstage: http://backstage.idpbuilder.cnoe.io.local/
Backstage: http://backstage.idpbuilder.cnoe.io.localtest.me/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it needs the port number here to connect to ingress-nginx

 http://backstage.idpbuilder.cnoe.io.localtest.me:8443

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes as the we expose on the kind cluster and docker the ports 8443 and 8880. Question: Why do you export on kind/docker such ports instead to keep the standards: 80 and 443 ?

Copy link
Contributor Author

@jessesanford jessesanford Oct 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good question. My guess is that they were using high number ports to avoid needing to be a privileged user on some systems

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Such ports should be configurable and defaulted within the kind config file to: 80, 443. I will open a separate issue about that

@nimakaviani
Copy link
Contributor

@jessesanford yeah I think the duplication is very confusing indeed. I think once we fix the README as @nabuskey pointed out, I am good with merging this for now.

@cmoulliard
Copy link
Contributor

Dont forget to change also the ingress host(s) if now we will use everywhere *.idpbuilder.cnoe.io.localtest.me/ ?

Copy link
Contributor

@nimakaviani nimakaviani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jessesanford jessesanford merged commit fd507f5 into main Oct 18, 2023
1 check failed

Backstage: http://backstage.idpbuilder.cnoe.io.local/
Backstage: http://backstage.idpbuilder.cnoe.io.localtest.me/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes as the we expose on the kind cluster and docker the ports 8443 and 8880. Question: Why do you export on kind/docker such ports instead to keep the standards: 80 and 443 ?

@@ -10,7 +10,7 @@ metadata:
spec:
ingressClassName: "nginx"
rules:
- host: argocd.idpbuilder.cnoe.io.local
- host: argocd.idpbuilder.cnoe.io.localtest.me
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to use a so long DNS name *.idpbuilder.cnoe.io.localtest.me vs *.idpbuilder.localtest.me or even better *.idp.localtest.me ?

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 this pull request may close these issues.

4 participants