-
Notifications
You must be signed in to change notification settings - Fork 208
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
Expose gitkube as NodePort type #36
Comments
@sdileep Can you paste the |
@coco98 This is not a minikube environment(mentioned it above). I'm running a couple VMs using VirtualBox and Vagrant. The VMs are on a private network with static IP addresses assigned to them. The cluster was created with @shahidhk The command that I used was
Since I don't have a load balancer, the remote url isn't generated I reckon. |
@sdileep Can you try setting this remote manually?
Also, it'll be helpful if you can paste relevant log lines from NodePort service objects does not have an external ip field in the spec. Hence gitkube might not be able to figure out the IP. But, this should have been reported as a message in the remote object status. |
Apart from this, as @shahidhk mentioned, we do not have the external ip for nodeport service in the service object. We can work around this by going through all the nodes and getting the ip of one of the nodes and filling it in the remote. PRs welcome for this. |
@shahidhk The logs from the controller are as follows:
Logs from gitkubed are as follows:
^^ those logs seems to keep repeating for every 4th port @shahidhk thanks for the git remote url, the one from the example doc is not correct. This solves the issue for me. |
I'm trying to experiment with gitkube on a local cluster(not minikube) and hence exposed it as NodePort type service. After creating a remote as per example, I am not able to retrieve the remote URL using
$ kubectl get remote example -o json | jq -r '.status.remoteUrl
. Am I missing something?ps: the example worked on GCE without any issues.
The text was updated successfully, but these errors were encountered: