Kubernetes using Gitlab installing Ingress returns “?” as external IP
I have successfully connect my Kubernetes-Cluster with Gitlab. Also I was able to install Helm through the Gitlab UI (Operations->Kubernetes)
My Problem is that if I click on the "Install"-Button of Ingress Gitlab will create all the nessecary stuff that is needed for the Ingress-Controller. But one thing will be missed : external IP. External IP will mark as "?".
And If I run this command:
kubectl get svc --namespace=gitlab-managed-apps ingress-nginx-ingress- controller -o jsonpath='{.status.loadBalancer.ingress[0].ip}'; echo
It will show nothing. Like I won´t have a Loadbalancer that exposes an external IP.
Kubernetes Cluster
I installed Kubernetes through kubeadm, using flannel as CNI
kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Is there something that I have to configure before installing Ingress. Do I need an external Loadbalancer(my thought: Gitlab will create that service for me)?
One more hint: After installation, the state of the Nginx-Ingress-Controller Service will be stay on pending. The reason for that it is not able to detect external IP. I also modified the yaml-File of the service and I manually put the "externalIPs : -External-IP line. The output of this was that it was not pending anymore. But still I couldn't find an external IP by typing the above command and Gitlab also couldn´t find any external IP
EDIT:
This happens after installation:
see picture
EDIT2:
By running the following command:
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
I get the following result:
see picture
In Event log you will see that I switch the type to "NodePort" once and then back to "LoadBalancer" and I added the "externalIPs: -192.168.50.235" line in the yaml file. As you can see there is an externalIP but Git is not detecting it.
Btw. Im not using any of these cloud providers like AWS or GCE and I found out that LoadBalancer is not working that way. But there must be a solution for this without LoadBalancer.
docker kubernetes continuous-integration gitlab nginx-ingress
add a comment |
I have successfully connect my Kubernetes-Cluster with Gitlab. Also I was able to install Helm through the Gitlab UI (Operations->Kubernetes)
My Problem is that if I click on the "Install"-Button of Ingress Gitlab will create all the nessecary stuff that is needed for the Ingress-Controller. But one thing will be missed : external IP. External IP will mark as "?".
And If I run this command:
kubectl get svc --namespace=gitlab-managed-apps ingress-nginx-ingress- controller -o jsonpath='{.status.loadBalancer.ingress[0].ip}'; echo
It will show nothing. Like I won´t have a Loadbalancer that exposes an external IP.
Kubernetes Cluster
I installed Kubernetes through kubeadm, using flannel as CNI
kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Is there something that I have to configure before installing Ingress. Do I need an external Loadbalancer(my thought: Gitlab will create that service for me)?
One more hint: After installation, the state of the Nginx-Ingress-Controller Service will be stay on pending. The reason for that it is not able to detect external IP. I also modified the yaml-File of the service and I manually put the "externalIPs : -External-IP line. The output of this was that it was not pending anymore. But still I couldn't find an external IP by typing the above command and Gitlab also couldn´t find any external IP
EDIT:
This happens after installation:
see picture
EDIT2:
By running the following command:
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
I get the following result:
see picture
In Event log you will see that I switch the type to "NodePort" once and then back to "LoadBalancer" and I added the "externalIPs: -192.168.50.235" line in the yaml file. As you can see there is an externalIP but Git is not detecting it.
Btw. Im not using any of these cloud providers like AWS or GCE and I found out that LoadBalancer is not working that way. But there must be a solution for this without LoadBalancer.
docker kubernetes continuous-integration gitlab nginx-ingress
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you checkkubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?
– mk_sta
Nov 19 '18 at 12:46
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00
add a comment |
I have successfully connect my Kubernetes-Cluster with Gitlab. Also I was able to install Helm through the Gitlab UI (Operations->Kubernetes)
My Problem is that if I click on the "Install"-Button of Ingress Gitlab will create all the nessecary stuff that is needed for the Ingress-Controller. But one thing will be missed : external IP. External IP will mark as "?".
And If I run this command:
kubectl get svc --namespace=gitlab-managed-apps ingress-nginx-ingress- controller -o jsonpath='{.status.loadBalancer.ingress[0].ip}'; echo
It will show nothing. Like I won´t have a Loadbalancer that exposes an external IP.
Kubernetes Cluster
I installed Kubernetes through kubeadm, using flannel as CNI
kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Is there something that I have to configure before installing Ingress. Do I need an external Loadbalancer(my thought: Gitlab will create that service for me)?
One more hint: After installation, the state of the Nginx-Ingress-Controller Service will be stay on pending. The reason for that it is not able to detect external IP. I also modified the yaml-File of the service and I manually put the "externalIPs : -External-IP line. The output of this was that it was not pending anymore. But still I couldn't find an external IP by typing the above command and Gitlab also couldn´t find any external IP
EDIT:
This happens after installation:
see picture
EDIT2:
By running the following command:
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
I get the following result:
see picture
In Event log you will see that I switch the type to "NodePort" once and then back to "LoadBalancer" and I added the "externalIPs: -192.168.50.235" line in the yaml file. As you can see there is an externalIP but Git is not detecting it.
Btw. Im not using any of these cloud providers like AWS or GCE and I found out that LoadBalancer is not working that way. But there must be a solution for this without LoadBalancer.
docker kubernetes continuous-integration gitlab nginx-ingress
I have successfully connect my Kubernetes-Cluster with Gitlab. Also I was able to install Helm through the Gitlab UI (Operations->Kubernetes)
My Problem is that if I click on the "Install"-Button of Ingress Gitlab will create all the nessecary stuff that is needed for the Ingress-Controller. But one thing will be missed : external IP. External IP will mark as "?".
And If I run this command:
kubectl get svc --namespace=gitlab-managed-apps ingress-nginx-ingress- controller -o jsonpath='{.status.loadBalancer.ingress[0].ip}'; echo
It will show nothing. Like I won´t have a Loadbalancer that exposes an external IP.
Kubernetes Cluster
I installed Kubernetes through kubeadm, using flannel as CNI
kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2"}
Is there something that I have to configure before installing Ingress. Do I need an external Loadbalancer(my thought: Gitlab will create that service for me)?
One more hint: After installation, the state of the Nginx-Ingress-Controller Service will be stay on pending. The reason for that it is not able to detect external IP. I also modified the yaml-File of the service and I manually put the "externalIPs : -External-IP line. The output of this was that it was not pending anymore. But still I couldn't find an external IP by typing the above command and Gitlab also couldn´t find any external IP
EDIT:
This happens after installation:
see picture
EDIT2:
By running the following command:
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
I get the following result:
see picture
In Event log you will see that I switch the type to "NodePort" once and then back to "LoadBalancer" and I added the "externalIPs: -192.168.50.235" line in the yaml file. As you can see there is an externalIP but Git is not detecting it.
Btw. Im not using any of these cloud providers like AWS or GCE and I found out that LoadBalancer is not working that way. But there must be a solution for this without LoadBalancer.
docker kubernetes continuous-integration gitlab nginx-ingress
docker kubernetes continuous-integration gitlab nginx-ingress
edited Nov 19 '18 at 13:38
Kubilay Anil
asked Nov 19 '18 at 9:23
Kubilay AnilKubilay Anil
186
186
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you checkkubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?
– mk_sta
Nov 19 '18 at 12:46
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00
add a comment |
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you checkkubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?
– mk_sta
Nov 19 '18 at 12:46
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you check
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?– mk_sta
Nov 19 '18 at 12:46
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you check
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?– mk_sta
Nov 19 '18 at 12:46
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00
add a comment |
2 Answers
2
active
oldest
votes
I would consider to look at MetalLB as for the main provisioner of Load balancing service in your cluster. If you don't use any of Cloud providers in order to obtain the entry point (External IP) for Ingress
resource, there is option for Bare-metal environments to switch to MetalLB
solution which will create Kubernetes services of type LoadBalancer
in the clusters that don’t run on a cloud provider, therefore it can be also implemented for NGINX Ingress Controller.
Generally, MetalLB
can be installed via Kubernetes manifest file or using Helm package manager as described here.
MetalLB
deploys it's own services across Kubernetes cluster and it might require to reserve pool of IP addresses in order to be able to take ownership of the ingress-nginx
service. This pool can be defined in a ConfigMap
called config
located in the same namespace as the MetalLB
controller:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 203.0.113.2-203.0.113.3
External IP would be assigned to your LoadBalancer
once ingress service obtains IP address from this address pool.
Find more details about MetalLB
implementation for NGINX Ingress Controller in official documentation.
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
add a comment |
After some research I found out that this is an Gitlab issue. As I said above, I successfully build a connection to my cluster. Since Im using Kubernetes without cloud providers it is not possible to use the type "LoadBalancer". Therefore you need to add an external IP or change the type to "NodePort". This way you can make your Ingress-Controller accessible outside.
Check this out: kubernetes service external ip pending
I just continued the Gitlab tutorial and it worked.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371576%2fkubernetes-using-gitlab-installing-ingress-returns-as-external-ip%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would consider to look at MetalLB as for the main provisioner of Load balancing service in your cluster. If you don't use any of Cloud providers in order to obtain the entry point (External IP) for Ingress
resource, there is option for Bare-metal environments to switch to MetalLB
solution which will create Kubernetes services of type LoadBalancer
in the clusters that don’t run on a cloud provider, therefore it can be also implemented for NGINX Ingress Controller.
Generally, MetalLB
can be installed via Kubernetes manifest file or using Helm package manager as described here.
MetalLB
deploys it's own services across Kubernetes cluster and it might require to reserve pool of IP addresses in order to be able to take ownership of the ingress-nginx
service. This pool can be defined in a ConfigMap
called config
located in the same namespace as the MetalLB
controller:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 203.0.113.2-203.0.113.3
External IP would be assigned to your LoadBalancer
once ingress service obtains IP address from this address pool.
Find more details about MetalLB
implementation for NGINX Ingress Controller in official documentation.
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
add a comment |
I would consider to look at MetalLB as for the main provisioner of Load balancing service in your cluster. If you don't use any of Cloud providers in order to obtain the entry point (External IP) for Ingress
resource, there is option for Bare-metal environments to switch to MetalLB
solution which will create Kubernetes services of type LoadBalancer
in the clusters that don’t run on a cloud provider, therefore it can be also implemented for NGINX Ingress Controller.
Generally, MetalLB
can be installed via Kubernetes manifest file or using Helm package manager as described here.
MetalLB
deploys it's own services across Kubernetes cluster and it might require to reserve pool of IP addresses in order to be able to take ownership of the ingress-nginx
service. This pool can be defined in a ConfigMap
called config
located in the same namespace as the MetalLB
controller:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 203.0.113.2-203.0.113.3
External IP would be assigned to your LoadBalancer
once ingress service obtains IP address from this address pool.
Find more details about MetalLB
implementation for NGINX Ingress Controller in official documentation.
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
add a comment |
I would consider to look at MetalLB as for the main provisioner of Load balancing service in your cluster. If you don't use any of Cloud providers in order to obtain the entry point (External IP) for Ingress
resource, there is option for Bare-metal environments to switch to MetalLB
solution which will create Kubernetes services of type LoadBalancer
in the clusters that don’t run on a cloud provider, therefore it can be also implemented for NGINX Ingress Controller.
Generally, MetalLB
can be installed via Kubernetes manifest file or using Helm package manager as described here.
MetalLB
deploys it's own services across Kubernetes cluster and it might require to reserve pool of IP addresses in order to be able to take ownership of the ingress-nginx
service. This pool can be defined in a ConfigMap
called config
located in the same namespace as the MetalLB
controller:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 203.0.113.2-203.0.113.3
External IP would be assigned to your LoadBalancer
once ingress service obtains IP address from this address pool.
Find more details about MetalLB
implementation for NGINX Ingress Controller in official documentation.
I would consider to look at MetalLB as for the main provisioner of Load balancing service in your cluster. If you don't use any of Cloud providers in order to obtain the entry point (External IP) for Ingress
resource, there is option for Bare-metal environments to switch to MetalLB
solution which will create Kubernetes services of type LoadBalancer
in the clusters that don’t run on a cloud provider, therefore it can be also implemented for NGINX Ingress Controller.
Generally, MetalLB
can be installed via Kubernetes manifest file or using Helm package manager as described here.
MetalLB
deploys it's own services across Kubernetes cluster and it might require to reserve pool of IP addresses in order to be able to take ownership of the ingress-nginx
service. This pool can be defined in a ConfigMap
called config
located in the same namespace as the MetalLB
controller:
apiVersion: v1
kind: ConfigMap
metadata:
namespace: metallb-system
name: config
data:
config: |
address-pools:
- name: default
protocol: layer2
addresses:
- 203.0.113.2-203.0.113.3
External IP would be assigned to your LoadBalancer
once ingress service obtains IP address from this address pool.
Find more details about MetalLB
implementation for NGINX Ingress Controller in official documentation.
answered Nov 20 '18 at 12:01
mk_stamk_sta
828128
828128
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
add a comment |
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Thanks! Will look about that.
– Kubilay Anil
Nov 20 '18 at 13:25
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Im facing a new issue. When I try to deploy something (via Gitlab) I get the following error: $ deploy Error: UPGRADE FAILED: no release provided ERROR: Job failed: error executing remote command: command terminated with non-zero exit code: Error executing in Docker Container: 1 Im using the default DevOps of Gitlab. In the Build Pipeling everything works fine. But when it comes to Production I get the error code above.
– Kubilay Anil
Nov 21 '18 at 15:39
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
Create separate question for this error, which is not connected with my answer here.
– mk_sta
Nov 22 '18 at 9:21
add a comment |
After some research I found out that this is an Gitlab issue. As I said above, I successfully build a connection to my cluster. Since Im using Kubernetes without cloud providers it is not possible to use the type "LoadBalancer". Therefore you need to add an external IP or change the type to "NodePort". This way you can make your Ingress-Controller accessible outside.
Check this out: kubernetes service external ip pending
I just continued the Gitlab tutorial and it worked.
add a comment |
After some research I found out that this is an Gitlab issue. As I said above, I successfully build a connection to my cluster. Since Im using Kubernetes without cloud providers it is not possible to use the type "LoadBalancer". Therefore you need to add an external IP or change the type to "NodePort". This way you can make your Ingress-Controller accessible outside.
Check this out: kubernetes service external ip pending
I just continued the Gitlab tutorial and it worked.
add a comment |
After some research I found out that this is an Gitlab issue. As I said above, I successfully build a connection to my cluster. Since Im using Kubernetes without cloud providers it is not possible to use the type "LoadBalancer". Therefore you need to add an external IP or change the type to "NodePort". This way you can make your Ingress-Controller accessible outside.
Check this out: kubernetes service external ip pending
I just continued the Gitlab tutorial and it worked.
After some research I found out that this is an Gitlab issue. As I said above, I successfully build a connection to my cluster. Since Im using Kubernetes without cloud providers it is not possible to use the type "LoadBalancer". Therefore you need to add an external IP or change the type to "NodePort". This way you can make your Ingress-Controller accessible outside.
Check this out: kubernetes service external ip pending
I just continued the Gitlab tutorial and it worked.
answered Nov 21 '18 at 15:31
Kubilay AnilKubilay Anil
186
186
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371576%2fkubernetes-using-gitlab-installing-ingress-returns-as-external-ip%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How did you provision k8s cluster (Cloud provider, bare-metal solutions)? Can you check
kubectl describe svc ingress-nginx-ingress-controller -n gitlab-managed-apps
?– mk_sta
Nov 19 '18 at 12:46
@mk_sta Im running Kubernetes on a Ubuntu 18.04.1 LTS (Bionic Beaver) virtual machine. Check the second Image to see the description.
– Kubilay Anil
Nov 19 '18 at 13:00