Repository navigation
Configure Core HTTPS routing on TKE #2
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| # Applied separately after DNS and the qcloud certificate reference are ready. | ||
| apiVersion: networking.k8s.io/v1 | ||
| kind: Ingress | ||
| metadata: | ||
| name: oac | ||
| labels: | ||
| app.kubernetes.io/part-of: openagentcore | ||
| annotations: | ||
| kubernetes.io/ingress.class: qcloud | ||
| kubernetes.io/ingress.existLbId: "${OAC_CLB_ID}" | ||
| ingress.cloud.tencent.com/enable-group: "true" | ||
| ingress.cloud.tencent.com/auto-rewrite: "true" | ||
| ingress.cloud.tencent.com/rewrite-support: "true" | ||
| kubernetes.io/ingress.rule-mix: "true" | ||
| kubernetes.io/ingress.extensiveParameters: '{"ConnectTimeout":300000,"SendTimeout":900000,"ReadTimeout":900000}' | ||
| kubernetes.io/ingress.http-rules: "null" | ||
| kubernetes.io/ingress.https-rules: | | ||
| [{"host":"${OAC_PUBLIC_HOST}","path":"/v1","backend":{"serviceName":"oac-core","servicePort":"8091"}}, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
If an operator sets AGENTS.md reference: AGENTS.md:L46-L46 Useful? React with 👍 / 👎. |
||
| {"host":"${OAC_PUBLIC_HOST}","path":"/api/v1","backend":{"serviceName":"oac-core","servicePort":"8091"}}, | ||
| {"host":"${OAC_PUBLIC_HOST}","path":"/","backend":{"serviceName":"oac-web","servicePort":"8080"}}] | ||
| spec: | ||
| ingressClassName: qcloud | ||
| tls: | ||
| - hosts: ["${OAC_PUBLIC_HOST}"] | ||
| secretName: "${OAC_TLS_SECRET}" | ||
| rules: | ||
| - host: "${OAC_PUBLIC_HOST}" | ||
| http: | ||
| paths: | ||
| - path: /v1 | ||
| pathType: Prefix | ||
| backend: | ||
| service: | ||
| name: oac-core | ||
| port: {number: 8091} | ||
| - path: /api/v1 | ||
| pathType: Prefix | ||
| backend: | ||
| service: | ||
| name: oac-core | ||
| port: {number: 8091} | ||
| - path: / | ||
| pathType: Prefix | ||
| backend: | ||
| service: | ||
| name: oac-web | ||
| port: {number: 8080} | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the reused CLB does not already have these timeout values, this annotation will not apply them: Tencent documents
kubernetes.io/ingress.extensiveParametersas parameters used only when creating a CLB and says changes after creation are ineffective, while this manifest explicitly selects an existing CLB withexistLbId(TKE Ingress annotations). Consequently, long HTTP streams and Runtime WebSocket connections remain subject to the existing listener defaults; configure the listener through a referencedTkeServiceConfigor make the existing-CLB prerequisite explicit instead.Useful? React with 👍 / 👎.