You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/11/22 06:49:55 UTC
[GitHub] [apisix] marksugar opened a new issue, #8372: help request: traffic-split blue-green not take effect
marksugar opened a new issue, #8372:
URL: https://github.com/apache/apisix/issues/8372
### Description
Server: APISIX/2.15.0
two sets of Pods in k8s called nginxa and nginxb, which is okay when I use backends for weighting
```
backends:
- serviceName: nginxb
servicePort: 80
weight: 40
- serviceName: nginxa
servicePort: 80
weight: 60
```
When I tried to use the plugins' traffic-split, it didn't work.
yaml is as follows
```
plugins:
- name: traffic-split
enable: true
config:
rules:
- match:
vars: ["http_release","==","new_release123"]
weighted_upstreams:
- name: nginxb
weight: 100
backends:
- serviceName: nginxb
servicePort: 80
```
In the routing of the dashboard, the data editor is represented as follows
```
{
"uris": [
"/*"
],
"name": "default_nginx_root",
"desc": "Created by apisix-ingress-controller, DO NOT modify it manually",
"hosts": [
"nginx.test.com"
],
"plugins": {
"traffic-split": {
"rules": [
{
"vars": [
"http_release",
"==",
"new_release123"
],
"weighted_upstreams": [
{
"name": "default_nginxb_80",
"nodes": [
"192.120.1.216"
],
"weight": 90
}
]
}
]
}
},
"upstream_id": "1b1fd9dd",
"labels": {
"managed-by": "apisix-ingress-controller"
},
"status": 1
}
```
Although this configuration does not throw an error, it does not do anything.
When I change the configuration as follows, the data in the data editor in the dashboard route does not change in any way
```
plugins:
- name: traffic-split
enable: true
config:
rules:
match:
- vars: ["http_release","==","new_release123"]
weighted_upstreams:
- upstream:
- name: nginxa
- type: roundrobin
- weight: 100
backends:
- serviceName: nginxb
servicePort: 80
```
so, What is the correct configuration to use YAML in K8S?
Thank you so much
### Environment
helm install apisix
version default
Server: APISIX/2.15.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] github-actions[bot] closed issue #8372: help request: traffic-split blue-green not take effect
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #8372: help request: traffic-split blue-green not take effect
URL: https://github.com/apache/apisix/issues/8372
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tokers commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1323379037
> When I tried to use the plugins' traffic-split, it didn't work.
Could you share the reason that you still use the traffic-split plugin even we have a better way to support the blue green deployment in APISIX Ingress Controller?
> Although this configuration does not throw an error, it does not do anything.
Have you ever seen the traffic-split plugin doc: https://apisix.apache.org/docs/apisix/plugins/traffic-split/. Your configuration fields are wrong. Indeed you have to specify the upstream id in the traffic-split plugin, which is not feasible when you use APISIX Ingress Controller as the ID generation is invisible to you. It's internal logic.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] marksugar commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by GitBox <gi...@apache.org>.
marksugar commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1324022355
> > When I tried to use the plugins' traffic-split, it didn't work.
>
> Could you share the reason that you still use the traffic-split plugin even we have a better way to support the blue green deployment in APISIX Ingress Controller?
>
> > Although this configuration does not throw an error, it does not do anything.
>
> Have you ever seen the traffic-split plugin doc: https://apisix.apache.org/docs/apisix/plugins/traffic-split/. Your configuration fields are wrong. Indeed you have to specify the upstream id in the traffic-split plugin, which is not feasible when you use APISIX Ingress Controller as the ID generation is invisible to you. It's internal logic.
tokers and tzssangglass ,thanks
Thanks for your reply, I just used apisix for a day and have two questions.
1, should we consider providing yaml configuration examples in the documentation?
This is very necessary in k8s configuration management
2, what is the better blue-green part referring to
If this question is too simple, please move to the discussion forum
best regards
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] shreemaan-abhishek commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by "shreemaan-abhishek (via GitHub)" <gi...@apache.org>.
shreemaan-abhishek commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1707980606
ping @marksugar
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tokers commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1324415337
> > > When I tried to use the plugins' traffic-split, it didn't work.
> >
> >
> > Could you share the reason that you still use the traffic-split plugin even we have a better way to support the blue green deployment in APISIX Ingress Controller?
> > > Although this configuration does not throw an error, it does not do anything.
> >
> >
> > Have you ever seen the traffic-split plugin doc: https://apisix.apache.org/docs/apisix/plugins/traffic-split/. Your configuration fields are wrong. Indeed you have to specify the upstream id in the traffic-split plugin, which is not feasible when you use APISIX Ingress Controller as the ID generation is invisible to you. It's internal logic.
>
> tokers and tzssangglass ,thanks Thanks for your reply, I just used apisix for a day and have two questions. 1, should we consider providing yaml configuration examples in the documentation? This is very necessary in k8s configuration management 2, what is the better blue-green part referring to
>
> If this question is too simple, please move to the discussion forum
>
> best regards
Yaml configuration for what? Already have the example for how you can use blue green deployment in APISIX Ingress Controller.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1323371303
It looks like the yaml configuration is formatted incorrectly rather than the plugin not taking effect?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] github-actions[bot] commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1735223652
Due to lack of the reporter's response this issue has been labeled with "no response". It will be close in 3 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] github-actions[bot] commented on issue #8372: help request: traffic-split blue-green not take effect
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8372:
URL: https://github.com/apache/apisix/issues/8372#issuecomment-1741730347
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org