nginx.ingress annotations not working for basic authentication in Kubernetes
I am trying to setup basic authentication on Kubernetes but the IP I obtain after setting up authentication using the nginx.ingress annotations is still publicly accessible. Below is the link I referred to in setting this up-
https://blog.bigbinary.com/2018/08/14/using-kubernetes-ingress-authentication.html
After following the process in the link, I should be prompted to enter the username and password when I hit that IP but instead I'm able to access it without any authentication.
nginx kubernetes gke
add a comment |
I am trying to setup basic authentication on Kubernetes but the IP I obtain after setting up authentication using the nginx.ingress annotations is still publicly accessible. Below is the link I referred to in setting this up-
https://blog.bigbinary.com/2018/08/14/using-kubernetes-ingress-authentication.html
After following the process in the link, I should be prompted to enter the username and password when I hit that IP but instead I'm able to access it without any authentication.
nginx kubernetes gke
add a comment |
I am trying to setup basic authentication on Kubernetes but the IP I obtain after setting up authentication using the nginx.ingress annotations is still publicly accessible. Below is the link I referred to in setting this up-
https://blog.bigbinary.com/2018/08/14/using-kubernetes-ingress-authentication.html
After following the process in the link, I should be prompted to enter the username and password when I hit that IP but instead I'm able to access it without any authentication.
nginx kubernetes gke
I am trying to setup basic authentication on Kubernetes but the IP I obtain after setting up authentication using the nginx.ingress annotations is still publicly accessible. Below is the link I referred to in setting this up-
https://blog.bigbinary.com/2018/08/14/using-kubernetes-ingress-authentication.html
After following the process in the link, I should be prompted to enter the username and password when I hit that IP but instead I'm able to access it without any authentication.
nginx kubernetes gke
nginx kubernetes gke
asked Nov 20 '18 at 16:43
Ben AbeyBen Abey
242
242
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I would recommend following this link which shows how to add authentication specific to GKE.
You can deploy an nginx ingress controller in your GKE cluster. Please make sure to annotate your ingress to avoid the GLBC claiming the ingress as specified in this link. Then you can expose the nginx controller directly, or create a glbc ingress to redirect traffic to the nginx ingress as specified in this link.
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%2f53397649%2fnginx-ingress-annotations-not-working-for-basic-authentication-in-kubernetes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would recommend following this link which shows how to add authentication specific to GKE.
You can deploy an nginx ingress controller in your GKE cluster. Please make sure to annotate your ingress to avoid the GLBC claiming the ingress as specified in this link. Then you can expose the nginx controller directly, or create a glbc ingress to redirect traffic to the nginx ingress as specified in this link.
add a comment |
I would recommend following this link which shows how to add authentication specific to GKE.
You can deploy an nginx ingress controller in your GKE cluster. Please make sure to annotate your ingress to avoid the GLBC claiming the ingress as specified in this link. Then you can expose the nginx controller directly, or create a glbc ingress to redirect traffic to the nginx ingress as specified in this link.
add a comment |
I would recommend following this link which shows how to add authentication specific to GKE.
You can deploy an nginx ingress controller in your GKE cluster. Please make sure to annotate your ingress to avoid the GLBC claiming the ingress as specified in this link. Then you can expose the nginx controller directly, or create a glbc ingress to redirect traffic to the nginx ingress as specified in this link.
I would recommend following this link which shows how to add authentication specific to GKE.
You can deploy an nginx ingress controller in your GKE cluster. Please make sure to annotate your ingress to avoid the GLBC claiming the ingress as specified in this link. Then you can expose the nginx controller directly, or create a glbc ingress to redirect traffic to the nginx ingress as specified in this link.
answered Nov 26 '18 at 21:22
John MathewJohn Mathew
1365
1365
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%2f53397649%2fnginx-ingress-annotations-not-working-for-basic-authentication-in-kubernetes%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