Merge branch 'main' into feat/substrate-python-byo

Author: EItanya

CONTRIBUTING.md

@@ -123,7 +123,7 @@ It's difficult to cover all the possible scenarios that you might encounter when
 
 DCO, short for Developer Certificate of Origin, is a per-commit signoff that you, the contributor, agree to the terms published at [https://developercertificate.org](https://developercertificate.org) for that particular commit. This will appear as a `Signed-off-by: Your Name <your.email>` trailer at the end of each commit message. The kagent project requires that every commit contains this DCO signoff.
 
-The easiest way to make sure each of your commits contains the signoff is to run make `init-git-hooks` in the repo to which you are contributing. This will configure your repo to use a Git hook which will automatically add the required trailer to all of your commit messages.
+The easiest way to make sure each of your commits contains the signoff is to run `make init-git-hooks` in the repo to which you are contributing. This will configure your repo to use a Git hook which will automatically add the required trailer to all of your commit messages.
 
 ```shell
 make init-git-hooks
@@ -229,7 +229,7 @@ All code must be reviewed by at least one [maintainer](https://github.com/kagent
 
 ## Documentation
 
-The kagent documentation lives at [kagent.dev/docs](https://kagent.dev/docs/kagent). The code lives at [kagent website](https://github.com/kagent-dev/website).
+The kagent documentation lives at [kagent.dev/docs/kagent](https://kagent.dev/docs/kagent). The code lives at [kagent website](https://github.com/kagent-dev/website).
 
 ## Get in touch
 

DEVELOPMENT.md

@@ -1,10 +1,10 @@
 # Development
 
-To understand how to develop for kagent, It's important to understand the architecture of the project. Please refer to the [README.md](README.md#architecture) file for an overview of the project.
+To understand how to develop for kagent, it's important to understand the architecture of the project. Please refer to the [README.md](README.md#architecture) file for an overview of the project.
 
 When making changes to `kagent`, the most important thing is to figure out which piece of the project is affected by the change, and then make the change in the appropriate folder. Each piece of the project has its own README with more information about how to setup the development environment and run that piece of the project.
 
-- [python](python): Contains the code for the ADK  engine.
+- [python](python): Contains the code for the ADK engine.
 - [go](go): Contains the code for the kubernetes controller, and the CLI.
 - [ui](ui): Contains the code for the web UI.
 

README.md

@@ -55,7 +55,7 @@
     </td>
   </tr>
 </table>
-<!-- markdownlint-disable MD033 -->
+<!-- markdownlint-enable MD033 -->
 
 ---
 
@@ -69,13 +69,13 @@
 ### Core Concepts
 
 - **Agents**: Agents are the main building block of kagent. They are a system prompt, a set of tools and agents, and an LLM configuration represented with a Kubernetes custom resource called "Agent".
-- **LLM Providers**: Kagent supports multiple LLM providers, including [OpenAI](https://kagent.dev/docs/kagent/supported-providers/openai), [Azure OpenAI](https://kagent.dev/docs/kagent/supported-providers/azure-openai), [Anthropic](https://kagent.dev/docs/kagent/supported-providers/anthropic), [Google Vertex AI](https://kagent.dev/docs/kagent/supported-providers/google-vertexai), [Ollama](https://kagent.dev/docs/kagent/supported-providers/ollama) and any other [custom providers and models](https://kagent.dev/docs/kagent/supported-providers/custom-models) accessible via AI gateways. Providers are represented by the ModelConfig resource.
+- **LLM Providers**: Kagent supports multiple LLM providers, including [OpenAI](https://kagent.dev/docs/kagent/supported-providers/openai), [Azure OpenAI](https://kagent.dev/docs/kagent/supported-providers/azure-openai), [Anthropic](https://kagent.dev/docs/kagent/supported-providers/anthropic), [Google Vertex AI](https://kagent.dev/docs/kagent/supported-providers/google-vertexai), [Ollama](https://kagent.dev/docs/kagent/supported-providers/ollama) and any other custom providers and models accessible via AI gateways. Providers are represented by the ModelConfig resource.
 - **MCP Tools**: Agents can connect to any MCP server that provides tools. Kagent comes with an MCP server with tools for Kubernetes, Istio, Helm, Argo, Prometheus, Grafana, Cilium, and others. All tools are Kubernetes custom resources (ToolServers) and can be used by multiple agents.
 - **Observability**: Kagent supports [OpenTelemetry tracing](https://kagent.dev/docs/kagent/getting-started/tracing), which allows you to monitor what's happening with your agents and tools.
 
 ### Core Principles
 
-- **Kubernetes Native**: Kagent is designed to be easy to understand and use, and to provide a flexible and powerful way to build and manage AI agents.
+- **Kubernetes Native**: Agents and tools are managed as Kubernetes custom resources using familiar `kubectl` workflows.
 - **Extensible**: Kagent is designed to be extensible, so you can add your own agents and tools.
 - **Flexible**: Kagent is designed to be flexible, to suit any AI agent use case.
 - **Observable**: Kagent is designed to be observable, so you can monitor the agents and tools using all common monitoring frameworks.
@@ -84,8 +84,6 @@
 
 ### Architecture
 
-The kagent framework is designed to be easy to understand and use, and to provide a flexible and powerful way to build and manage AI agents.
-
 <div align="center">
   <img src="img/arch.png" alt="kagent" width="500">
 </div>

SECURITY.md

@@ -10,31 +10,31 @@ To report a security vulnerability, email the private Google group kagent-vulner
 
 Send a report when:
 
-    You discover that a kagent component has a potential security vulnerability.
-    You are unsure whether or how a vulnerability affects kagent.
+- You discover that a kagent component has a potential security vulnerability.
+- You are unsure whether or how a vulnerability affects kagent.
 
 ### 🔔 Check before sending
 
 If in doubt, send a private message about potential vulnerabilities such as:
 
-    Any crash, especially in kagent.
-    Any potential Denial of Service (DoS) attack.
+- Any crash, especially in kagent.
+- Any potential Denial of Service (DoS) attack.
 
 ### ❌ When NOT to send a report
 
 Do not send a report for vulnerabilities that are not part of the kagent project, such as:
 
-    You want help configuring kagent components for security purposes.
-    You want help applying security related updates to your kagent configuration or environment.
-    Your issue is not related to security vulnerabilities.
-    Your issue is related to base image dependencies, such as AutoGen.
+- You want help configuring kagent components for security purposes.
+- You want help applying security related updates to your kagent configuration or environment.
+- Your issue is not related to security vulnerabilities.
+- Your issue is related to base image dependencies, such as AutoGen.
 
 ### Evaluation
 
 The kagent team evaluates vulnerability reports for:
 
-    Severity level, which can affect the priority of the fix
-    Impact of the vulnerability on kagent code as opposed to backend code
-    Potential dependencies on third-party or backend code that might delay the remediation process
+- Severity level, which can affect the priority of the fix
+- Impact of the vulnerability on kagent code as opposed to backend code
+- Potential dependencies on third-party or backend code that might delay the remediation process
 
 The kagent team strives to keep private any vulnerability information with us as part of the remediation process. We only share information on a need-to-know basis to address the issue.

contrib/README.md

@@ -18,7 +18,7 @@ To add your own contribution:
 3. Include a README.md in your subdirectory describing your contribution.
 4. Submit a pull request with a clear description of your changes.
 
-For more details, see the main `CONTRIBUTION.md` in the project root.
+For more details, see the main `CONTRIBUTING.md` in the project root.
 
 ---
 

helm/README.md

@@ -1,6 +1,6 @@
 # Kagent Helm Chart
 
-These Helm charts install kagent-crds,kagent, it is required that the Kagent CRDs chart to be installed first.
+These Helm charts install kagent-crds and kagent. The kagent-crds chart must be installed first.
 
 ## Installation
 
@@ -10,8 +10,8 @@ These Helm charts install kagent-crds,kagent, it is required that the Kagent CRD
 # First, install the required CRDs
 helm install kagent-crds ./helm/kagent-crds/  --namespace kagent
 
-# Then install Kagent with default provider 
-# --set providers.default=openAI enabled by default, but you need to provide your openAI apikey
+# Then install kagent with default provider
+# --set providers.default=openAI is enabled by default, but you need to provide your OpenAI API key
 helm install kagent ./helm/kagent/ --namespace kagent --set providers.openAI.apiKey=your-openai-api-key
 
 # Or with optional providers if you prefer local ollama provider or anthropic
@@ -35,7 +35,7 @@ make KAGENT_DEFAULT_MODEL_PROVIDER=openAI helm-install
 # install charts with anthropic provider
 make KAGENT_DEFAULT_MODEL_PROVIDER=anthropic helm-install
 
-# install charts with anthropic provider
+# install charts with azureOpenAI provider
 make KAGENT_DEFAULT_MODEL_PROVIDER=azureOpenAI helm-install
 
 # install charts with ollama provider

helm/kagent/files/nginx.conf

@@ -47,8 +47,8 @@ http {
             proxy_set_header X-Forwarded-Proto $scheme;
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_set_header Origin $scheme://$host;
-            proxy_read_timeout 600s;
-            proxy_send_timeout 600s;
+            proxy_read_timeout {{ .Values.ui.nginx.proxyReadTimeout }};
+            proxy_send_timeout {{ .Values.ui.nginx.proxySendTimeout }};
             proxy_buffering off;
         }
 
@@ -63,6 +63,10 @@ http {
             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_set_header Origin $scheme://$host;
             proxy_cache_bypass $http_upgrade;
+            # Increased timeouts for streaming endpoints
+            proxy_read_timeout {{ .Values.ui.nginx.proxyReadTimeout }};
+            proxy_send_timeout {{ .Values.ui.nginx.proxySendTimeout }};
+            proxy_buffering off;
         }
 
         location /health {
@@ -80,8 +84,8 @@ http {
             proxy_set_header X-Forwarded-Proto $scheme;
             proxy_set_header X-Forwarded-Host $server_name;
             proxy_cache_bypass $http_upgrade;
-            proxy_read_timeout 3600s;
-            proxy_send_timeout 3600s;
+            proxy_read_timeout {{ .Values.ui.nginx.proxyReadTimeout }};
+            proxy_send_timeout {{ .Values.ui.nginx.proxySendTimeout }};
             proxy_buffering off;
         }
     }

helm/kagent/templates/openshift-route.yaml

@@ -6,6 +6,10 @@ kind: Route
 metadata:
     name: {{ include "kagent.fullname" . }}-ui
     namespace: {{ include "kagent.namespace" . }}
+    {{- with .Values.ui.openshiftRoute.annotations }}
+    annotations:
+      {{- toYaml . | nindent 6 }}
+    {{- end }}
 spec:
     to:
         kind: Service

helm/kagent/templates/ui-deployment.yaml

@@ -64,6 +64,10 @@ spec:
             - name: SSO_REDIRECT_PATH
               value: {{ .Values.ui.auth.ssoRedirectPath | default "/oauth2/start" | quote }}
             {{- end }}
+            {{- if .Values.ui.streamTimeoutSeconds }}
+            - name: KAGENT_STREAM_TIMEOUT_MS
+              value: {{ mul (int .Values.ui.streamTimeoutSeconds) 1000 | quote }}
+            {{- end }}
             {{- with .Values.ui.additionalForwardedHeaders }}
             - name: KAGENT_ADDITIONAL_FORWARDED_HEADERS
               value: {{ join "," . | quote }}

helm/kagent/values.yaml

@@ -351,6 +351,17 @@ ui:
     # Path to redirect users to when they click "Sign in with SSO" on the login page
     # Default: /oauth2/start (oauth2-proxy's authentication start endpoint)
     ssoRedirectPath: "/oauth2/start"
+  # -- Client-side chat stream inactivity timeout (seconds). The browser aborts a
+  # streaming response if no event is received within this window. Should be >=
+  # ui.nginx.proxyReadTimeout so nginx isn't the silent limit. Default 1800 (30m).
+  streamTimeoutSeconds: 1800
+  # -- Nginx proxy timeout configuration for the UI sidecar (values are passed
+  # directly to the corresponding nginx directives, e.g. "1800s").
+  nginx:
+    # -- proxy_read_timeout: max time between two successive reads from the upstream.
+    proxyReadTimeout: 1800s
+    # -- proxy_send_timeout: max time between two successive writes to the upstream.
+    proxySendTimeout: 1800s
   env: {} # Additional configuration key-value pairs for the ui ConfigMap
   # -- Additional request headers (beyond Authorization) the UI proxy will forward
   # to the backend. Names are case-insensitive. Hop-by-hop headers (Connection,
@@ -419,6 +430,13 @@ ui:
   # oauth2-proxy instead of the chart's edge-terminated Route.
   route:
     enabled: true
+  
+  # OpenShift Route only (when route.openshift.io/v1 exists). Long timeouts are required
+  # for A2A/SSE streaming through the cluster router; defaults are often ~60s and cause
+  # net::ERR_INCOMPLETE_CHUNKED_ENCODING in the browser.
+  openshiftRoute:
+    annotations:
+      haproxy.router.openshift.io/timeout: 120m
 # ==============================================================================
 # LLM PROVIDERS CONFIGURATION
 # ==============================================================================