-
Notifications
You must be signed in to change notification settings - Fork 43
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
controller: updates the status of CRDs with reconciliation result #130
Comments
/assign |
@daixiang0 are you still interested in this? i think we could use your help |
Sure, I will do it |
Great! |
mathetake
added a commit
that referenced
this issue
Feb 25, 2025
**Commit Message** Update AIGatewayRoute status during reconcile. **Related Issues/PRs (if applicable)** Contributes to #130 --------- Signed-off-by: Loong <[email protected]> Co-authored-by: Takeshi Yoneda <[email protected]>
mathetake
added a commit
that referenced
this issue
Feb 26, 2025
**Commit Message** This adds the status fields to BackendSecurityPolicy and AIServiceBackend just like we already have for AIGatewayRoute since #187. The output will look like ``` $ k get aiservicebackends.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws Accepted envoy-ai-gateway-basic-openai Accepted envoy-ai-gateway-basic-testupstream Accepted $ k get backendsecuritypolicies.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws-credentials Accepted envoy-ai-gateway-basic-openai-apikey Accepted $ k get aigatewayroutes.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic Accepted ``` **Related Issues/PRs (if applicable)** Follow up on #187 and closes #130 --------- Signed-off-by: Takeshi Yoneda <[email protected]>
daixiang0
pushed a commit
to daixiang0/ai-gateway
that referenced
this issue
Feb 27, 2025
**Commit Message** This adds the status fields to BackendSecurityPolicy and AIServiceBackend just like we already have for AIGatewayRoute since envoyproxy#187. The output will look like ``` $ k get aiservicebackends.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws Accepted envoy-ai-gateway-basic-openai Accepted envoy-ai-gateway-basic-testupstream Accepted $ k get backendsecuritypolicies.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws-credentials Accepted envoy-ai-gateway-basic-openai-apikey Accepted $ k get aigatewayroutes.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic Accepted ``` **Related Issues/PRs (if applicable)** Follow up on envoyproxy#187 and closes envoyproxy#130 --------- Signed-off-by: Takeshi Yoneda <[email protected]>
daixiang0
pushed a commit
to daixiang0/ai-gateway
that referenced
this issue
Feb 27, 2025
**Commit Message** This adds the status fields to BackendSecurityPolicy and AIServiceBackend just like we already have for AIGatewayRoute since envoyproxy#187. The output will look like ``` $ k get aiservicebackends.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws Accepted envoy-ai-gateway-basic-openai Accepted envoy-ai-gateway-basic-testupstream Accepted $ k get backendsecuritypolicies.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic-aws-credentials Accepted envoy-ai-gateway-basic-openai-apikey Accepted $ k get aigatewayroutes.aigateway.envoyproxy.io NAME STATUS envoy-ai-gateway-basic Accepted ``` **Related Issues/PRs (if applicable)** Follow up on envoyproxy#187 and closes envoyproxy#130 --------- Signed-off-by: Takeshi Yoneda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: