-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
Whitelists are not working #9402
Comments
I encountered this problem on 1.0.0 too. |
@KevinKlinger & @oulinbao I have tried 1.0.2 and 1.0.3. they are not working. But it works in |
/assign @kyessenov |
I have tried the task but failed to reproduce the issue on 1.0.3. After creating the handler/instance/rule, I can see black starts only when I login as user "jason", and no stars, otherwise. A few things that can help us to debug further:
- args:
- --address
- unix:///sock/mixer.socket
- --configStoreURL=k8s://
- --configDefaultNamespace=istio-system
- --trace_zipkin_url=http://zipkin:9411/api/v1/spans
- --log_output_level=api:debug
|
I guess that is relevant with the cache. I meet this issue in the first time, it works after. Then I delete |
Logout the productpage. re-apply the whitelist handler, it still show red stars. Here are logs:
It works after a few minutes. |
Thanks for the logs. The log line that stands out to me is at the bottom "Publishing 3 events". It seems that Mixer received the config deletion events fairly late in the log. That means Mixer was operating with the old config state prior to receiving the events. This happens with a loaded API server that introduces a significant latency between kubectl commands and clients actually receiving the new state. Note that check decisions are indeed cached:
You can change it with |
@kyessenov Thanks for your explanations. |
Is there still an issue observed if we eliminate API server latency and caching duration? |
There is no an issue from my view. I think we can close this issue if the Author (@KevinKlinger ) has no concerns. |
I'm fine with your explanation. |
Describe the bug
I performed all actions as described in the docs.
The thing is I can get reviews with stars, which is definitely not intended.
It seems like all of my whitelists are not working since I tried others like the one described in #7766
Expected behavior
For the example in the docs I expected to see the productpage without stars, if I am not logged in as user jason.
For the example of #7766 I expected to get a 404 until I send requests with the correct x-api-key header.
Both configurations don't have any effect to the system.
Version
Istio: 1.0.2
K8s: 1.11.3
Installation
helm template install/kubernetes/helm/istio --name istio --namespace istio-system \
--set global.configValidation=false \
--set sidecarInjectorWebhook.enabled=false \
--set tracing.enabled=true \
--set tracing.jaeger.enabled=true \
--set kiali.enabled=false \
--set grafana.enabled=true
Environment
K8s, AWS
The text was updated successfully, but these errors were encountered: