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

how to access application only for VPN user.. #10155

Closed
techsachin1 opened this issue Jun 30, 2023 · 9 comments
Closed

how to access application only for VPN user.. #10155

techsachin1 opened this issue Jun 30, 2023 · 9 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@techsachin1
Copy link

one of my application is access by external users. i have to restrict that application to VPN user only.. i tried with whielist but when i apply whitlist in annotation it block all user. kindly suggest me what to do

this is my ingress rule
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: kafdrop-ingress
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/whitelist-source-range: x.x.x.x/32 (VPN user ip range)
spec:
tls:

hosts:
abc-a.xyz
secretName: kafdrop-tls
rules:
host: abc-a.xy
http:
paths:

  • pathType: Prefix
    path: "/"
    backend:
    service:
    name: kafdrop
    port:
    number: 9000
    this is my configuration... iam using Load balance also. when i apply this , all traffic get blocked after putting whitelist annotation.. please suggest way . i need to only VPN user to access this abc-a.xyz url
@techsachin1 techsachin1 added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 30, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jun 30, 2023
@cariorus
Copy link

cariorus commented Jul 8, 2023

#2096 (comment)

Hello, i think that is a bug.
"ingress.kubernetes.io/whitelist-source-range" can work !

@cariorus
Copy link

cariorus commented Jul 8, 2023

I apology give you error message, resolve

  1. kubectl describe service ingress-nginx-controller -n ingress-nginx
  2. External Traffic Policy Values need is: Local, not Cluster

my use helm deploy

  helm -n ingress-nginx upgrade --install ingress-nginx ingress-nginx/ingress-nginx \
      --set controller.service.externalTrafficPolicy=Local

@github-actions
Copy link

github-actions bot commented Aug 8, 2023

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 8, 2023
@sensyblee
Copy link

sensyblee commented Mar 21, 2024

I apology give you error message, resolve

  1. kubectl describe service ingress-nginx-controller -n ingress-nginx
  2. External Traffic Policy Values need is: Local, not Cluster

my use helm deploy

  helm -n ingress-nginx upgrade --install ingress-nginx ingress-nginx/ingress-nginx \
      --set controller.service.externalTrafficPolicy=Local

this worked for me, thank you
I did not use helm, instead i updated this option on ingress-nginx-controller service

@cariorus
Copy link

cariorus commented Mar 21, 2024

I apology give you error message, resolve

  1. kubectl describe service ingress-nginx-controller -n ingress-nginx
  2. External Traffic Policy Values need is: Local, not Cluster

my use helm deploy

  helm -n ingress-nginx upgrade --install ingress-nginx ingress-nginx/ingress-nginx \
      --set controller.service.externalTrafficPolicy=Local

this worked for me, thank you I did not use helm, instead i updated this option on ingress-nginx-controller service

you're welcome 😁

@yoges24
Copy link

yoges24 commented Jun 25, 2024

I did the same but its not working for me. I have updated the externalTrafficPolicy from Cluster to Local

@longwuyuan
Copy link
Contributor

No action item for project here.

/remove-kind feature
/kind support
/close

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Sep 13, 2024
@k8s-ci-robot
Copy link
Contributor

@longwuyuan: Closing this issue.

In response to this:

No action item for project here.

/remove-kind feature
/kind support
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

6 participants