content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
set to `"true"`. !!! note For more information please see [global-auth-url](./configmap.md#global-auth-url). ### Rate Limiting These annotations define limits on connections and transmission rates. These can be used to mitigate [DDoS Attacks](https://www.nginx.com/blog/mitigating-ddos-attacks-with-nginx-and-nginx-plus)... | null | main | kubernetes-ingress-nginx | [
-0.03415728360414505,
0.015398016199469566,
0.009560229256749153,
-0.026835501194000244,
-0.025415346026420593,
-0.08647630363702774,
-0.012970137409865856,
-0.009425394237041473,
0.07630819827318192,
0.06280215084552765,
0.004464976489543915,
-0.008359166793525219,
0.034021131694316864,
-... | 0.129352 |
the [`--enable-ssl-passthrough`](../cli-arguments.md) flag. !!! attention Because SSL Passthrough works on layer 4 of the OSI model (TCP) and not on the layer 7 (HTTP), using SSL Passthrough invalidates all the other annotations set on an Ingress object. ### Service Upstream By default the Ingress-Nginx Controller uses... | null | main | kubernetes-ingress-nginx | [
-0.057238392531871796,
0.07781442254781723,
0.0576266348361969,
0.0090551832690835,
-0.00884296465665102,
-0.023312505334615707,
0.0157930888235569,
-0.07823998481035233,
0.09074623882770538,
-0.004017950501292944,
-0.06874249875545502,
-0.04567465931177139,
0.03175528347492218,
0.08693006... | 0.048989 |
required to have different values. To allow this we provide annotations that allows this customization: - `nginx.ingress.kubernetes.io/proxy-connect-timeout` - `nginx.ingress.kubernetes.io/proxy-send-timeout` - `nginx.ingress.kubernetes.io/proxy-read-timeout` - `nginx.ingress.kubernetes.io/proxy-next-upstream` - `nginx... | null | main | kubernetes-ingress-nginx | [
-0.04075191169977188,
0.048121266067028046,
0.019521933048963547,
-0.030866174027323723,
-0.08626077324151993,
0.005118895787745714,
0.02973252907395363,
-0.030902007594704628,
0.08547093719244003,
0.025250671431422234,
-0.10593516379594803,
-0.021048009395599365,
-0.028860704973340034,
0.... | 0.095861 |
set by the `proxy\_buffer\_size` and `proxy\_buffers` directives. To configure this setting globally, set `proxy-busy-buffers-size` in the [ConfigMap](./configmap.md#proxy-busy-buffers-size). To use custom values in an Ingress rule, define this annotation: ```yaml nginx.ingress.kubernetes.io/proxy-busy-buffers-size: "1... | null | main | kubernetes-ingress-nginx | [
0.02025332860648632,
0.030895577743649483,
0.048132382333278656,
-0.010876612737774849,
-0.06582628935575485,
-0.07671047002077103,
0.005683321505784988,
0.007499305065721273,
0.052063606679439545,
0.11150626093149185,
-0.07225469499826431,
-0.018355080857872963,
-0.06345734000205994,
-0.0... | 0.068927 |
run in "Detection-Only" mode using the [recommended configuration](https://github.com/owasp-modsecurity/ModSecurity/blob/v3/master/modsecurity.conf-recommended). You can enable the [OWASP Core Rule Set](https://www.modsecurity.org/CRS/Documentation/) by setting the following annotation: ```yaml nginx.ingress.kubernetes... | null | main | kubernetes-ingress-nginx | [
-0.039180949330329895,
0.06714107096195221,
-0.03567548841238022,
0.02597128599882126,
0.04295261949300766,
-0.04616079851984978,
0.09150754660367966,
-0.0070610386319458485,
0.10460678488016129,
0.018870409578084946,
0.013713610358536243,
-0.06460563838481903,
0.03155644237995148,
0.02993... | 0.138574 |
# Custom NGINX template The NGINX template is located in the file `/etc/nginx/template/nginx.tmpl`. Using a [Volume](https://kubernetes.io/docs/concepts/storage/volumes/) it is possible to use a custom template. This includes using a [Configmap](https://kubernetes.io/docs/concepts/storage/volumes/#example-pod-with-a-se... | null | main | kubernetes-ingress-nginx | [
-0.0199973713606596,
0.08175598829984665,
0.03458349406719208,
-0.018605921417474747,
-0.039528585970401764,
0.016608433797955513,
-0.02762744575738907,
0.03971094638109207,
0.11449599266052246,
0.037801921367645264,
-0.036354370415210724,
-0.02527473121881485,
-0.024473119527101517,
0.040... | 0.076364 |
# Log format The default configuration uses a custom logging format to add additional information about upstreams, response time and status. ``` log\_format upstreaminfo '$remote\_addr - $remote\_user [$time\_local] "$request" ' '$status $body\_bytes\_sent "$http\_referer" "$http\_user\_agent" ' '$request\_length $requ... | null | main | kubernetes-ingress-nginx | [
-0.01136286836117506,
0.01952502317726612,
-0.013569864444434643,
-0.007688861805945635,
-0.046367619186639786,
-0.035258207470178604,
0.016050726175308228,
0.03671945258975029,
0.006595564540475607,
0.07644233107566833,
-0.04002491384744644,
-0.0481250062584877,
0.013386218808591366,
0.02... | 0.006912 |
# NGINX Configuration There are three ways to customize NGINX: 1. [ConfigMap](./configmap.md): using a Configmap to set global configurations in NGINX. 2. [Annotations](./annotations.md): use this if you want a specific configuration for a particular Ingress rule. 3. [Custom template](./custom-template.md): when more s... | null | main | kubernetes-ingress-nginx | [
-0.030192578211426735,
0.11479431390762329,
0.010117239318788052,
-0.061701349914073944,
0.018294934183359146,
0.023270605131983757,
0.015294747427105904,
0.04036718234419823,
-0.008006570860743523,
0.09674620628356934,
-0.0889422819018364,
-0.015187287703156471,
0.00021311324962880462,
-0... | 0.102866 |
# ModSecurity Web Application Firewall ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx that is developed by OWASP. It has a robust event-based programming language which provides protection from a range of attacks against web applications and allows for HTTP... | null | main | kubernetes-ingress-nginx | [
-0.09056887775659561,
0.024594813585281372,
-0.09321696311235428,
-0.023922841995954514,
0.09086974710226059,
-0.06472813338041306,
0.10251853615045547,
0.019624138250947,
0.03223622590303421,
0.005640100687742233,
0.043112464249134064,
-0.008040634915232658,
0.06596869975328445,
0.0647731... | 0.159819 |
# OpenTelemetry Enables requests served by NGINX for distributed telemetry via The OpenTelemetry Project. Using the third party module [opentelemetry-cpp-contrib/nginx](https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx) the Ingress-Nginx Controller can configure NGINX to enable... | null | main | kubernetes-ingress-nginx | [
-0.04316604882478714,
0.033314719796180725,
0.020284419879317284,
0.0010787721257656813,
-0.02466542087495327,
-0.08821281790733337,
-0.003612315049394965,
-0.0035959172528237104,
0.018895400688052177,
0.04860139265656471,
-0.024655554443597794,
-0.04880440607666969,
-0.02006208524107933,
... | 0.189492 |
add helm charts needed for grafana and OpenTelemetry collector helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts helm repo add grafana https://grafana.github.io/helm-charts helm repo update # deploy cert-manager needed for OpenTelemetry collector operator kubectl apply -f https://g... | null | main | kubernetes-ingress-nginx | [
-0.035699497908353806,
0.05870752036571503,
-0.01355066243559122,
-0.03295327350497246,
-0.0646430179476738,
-0.07748333364725113,
-0.08917682617902756,
-0.02171974442899227,
0.045475248247385025,
0.04147307947278023,
0.028960568830370903,
-0.15913952887058258,
-0.029176566749811172,
0.014... | 0.074063 |
# Hardening Guide Do not use in multi-tenant Kubernetes production installations. This project assumes that users that can create Ingress objects are administrators of the cluster. ## Overview There are several ways to do hardening and securing of nginx. In this documentation two guides are used, the guides are overlap... | null | main | kubernetes-ingress-nginx | [
-0.07558131963014603,
0.04772220551967621,
0.029199982061982155,
0.00034418204450048506,
-0.012964013032615185,
-0.042707622051239014,
0.01793782226741314,
-0.006844700779765844,
-0.002129613421857357,
-0.012022269889712334,
-0.010732152499258518,
-0.02572922222316265,
0.026227060705423355,
... | 0.138006 |
controller needs to update the configs dynamically| | | 2.3.2 Ensure access to NGINX directories and files is restricted (Scored) | OK | See previous answer| | | 2.3.3 Ensure the NGINX process ID (PID) file is secured (Scored)| OK | No PID-File due to docker design | | | 2.3.4 Ensure the core dump directory is secured ... | null | main | kubernetes-ingress-nginx | [
-0.028548071160912514,
0.029004884883761406,
-0.033395469188690186,
-0.023444795981049538,
0.02743213251233101,
-0.03444913774728775,
-0.07833513617515564,
-0.02377699874341488,
-0.011759391985833645,
0.07534068822860718,
-0.025153230875730515,
-0.039877116680145264,
0.0036398242227733135,
... | -0.023664 |
default | | | 4.1.2 Ensure a trusted certificate and trust chain is installed (Not Scored)| ACTION NEEDED| For installing certs there are enough manuals in the web. A good way is to use lets encrypt through cert-manager | Install proper certificates or use lets encrypt with cert-manager | | 4.1.3 Ensure private key per... | null | main | kubernetes-ingress-nginx | [
-0.036681488156318665,
0.044118721038103104,
-0.0785718485713005,
0.006142486352473497,
-0.027582161128520966,
-0.009293771348893642,
-0.05592853203415871,
0.0471014678478241,
-0.026585308834910393,
-0.008602669462561607,
0.017002051696181297,
-0.051630791276693344,
0.021943695843219757,
0... | -0.022379 |
| ACTION NEEDED| Default timeout is 60s | Set via [this configuration parameter](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/configmap.md#client-header-timeout) and respective body equivalent| | 5.2.2 Ensure the maximum request body size is set correctly (Scored)| ACTION NE... | null | main | kubernetes-ingress-nginx | [
-0.011432708241045475,
0.07537003606557846,
0.015570349991321564,
0.0044554369524121284,
-0.09244698286056519,
-0.03531093895435333,
-0.03386332467198372,
0.05139639601111412,
0.01776418648660183,
0.08170057088136673,
-0.07144361734390259,
-0.020372111350297928,
-0.0011378936469554901,
-0.... | 0.131175 |
# Installation Guide There are multiple ways to install the Ingress-Nginx Controller: - with [Helm](https://helm.sh), using the project repository chart; - with `kubectl apply`, using YAML manifests; - with specific addons (e.g. for [minikube](#minikube) or [MicroK8s](#microk8s)). On most Kubernetes clusters, the ingre... | null | main | kubernetes-ingress-nginx | [
0.02402094192802906,
0.034876495599746704,
0.04215467721223831,
-0.019294200465083122,
0.031508225947618484,
-0.011554372496902943,
-0.058072708547115326,
0.03346419706940651,
0.04183849319815636,
0.09980680048465729,
-0.02595263347029686,
-0.05982322618365288,
0.003034658497199416,
-0.022... | 0.069973 |
public on the kubernetes nodes to which the DNS of your apps are pointing. ### Pre-flight check A few pods should start in the `ingress-nginx` namespace: ```console kubectl get pods --namespace=ingress-nginx ``` After a while, they should all be running. The following command will wait for the ingress controller pod to... | null | main | kubernetes-ingress-nginx | [
0.00478355260565877,
-0.007428251672536135,
0.038203321397304535,
-0.02245146594941616,
-0.05254806578159332,
-0.05468367412686348,
-0.04888220131397247,
-0.02022910676896572,
0.08782786875963211,
0.11712921410799026,
-0.02866852842271328,
-0.0797877311706543,
-0.027259595692157745,
-0.028... | 0.123552 |
Desktop Kubernetes is available in Docker Desktop: - Mac, from [version 18.06.0-ce](https://docs.docker.com/docker-for-mac/release-notes/#stable-releases-of-2018) - Windows, from [version 18.06.0-ce](https://docs.docker.com/docker-for-windows/release-notes/#docker-community-edition-18060-ce-win70-2018-07-25) First, mak... | null | main | kubernetes-ingress-nginx | [
-0.04757099226117134,
0.06065788120031357,
0.01706589199602604,
-0.036225397139787674,
-0.007633620873093605,
-0.008694431744515896,
-0.0665447860956192,
-0.023072849959135056,
0.08049921691417694,
0.0487930104136467,
-0.03293927013874054,
-0.09253790229558945,
-0.007025785278528929,
-0.01... | 0.027272 |
ensure the [keepalive\_timeout](https://nginx.org/en/docs/http/ngx\_http\_core\_module.html#keepalive\_timeout) value is configured less than your configured idle timeout to work as expected. By default, NGINX `keepalive\_timeout` is set to `75s`. More information with regard to timeouts can be found in the [official A... | null | main | kubernetes-ingress-nginx | [
-0.011564590036869049,
0.04569198191165924,
0.010373331606388092,
-0.03413236141204834,
-0.035200513899326324,
-0.04045488312840462,
-0.011109860613942146,
-0.026906702667474747,
0.04028930515050888,
0.02582440711557865,
-0.09635482728481293,
-0.03937617316842079,
-0.007121207192540169,
-0... | 0.074303 |
`kubectl exec`: ```console POD\_NAMESPACE=ingress-nginx POD\_NAME=$(kubectl get pods -n $POD\_NAMESPACE -l app.kubernetes.io/name=ingress-nginx --field-selector=status.phase=Running -o name) kubectl exec $POD\_NAME -n $POD\_NAMESPACE -- /nginx-ingress-controller --version ``` ### Scope By default, the controller watche... | null | main | kubernetes-ingress-nginx | [
-0.010871452279388905,
-0.0013122066156938672,
0.015526174567639828,
0.033890482038259506,
0.006797869224101305,
-0.02232980914413929,
0.0073124440386891365,
-0.04529640078544617,
0.1205003634095192,
0.0662471204996109,
0.004138042218983173,
-0.0865844264626503,
0.023668790236115456,
-0.01... | 0.071631 |
# Role Based Access Control (RBAC) ## Overview This example applies to ingress-nginx-controllers being deployed in an environment with RBAC enabled. Role Based Access Control is comprised of four layers: 1. `ClusterRole` - permissions assigned to a role that apply to an entire cluster 2. `ClusterRoleBinding` - binding ... | null | main | kubernetes-ingress-nginx | [
-0.08413798362016678,
-0.04293042793869972,
-0.07847636938095093,
0.03190253674983978,
-0.03884272649884224,
0.03644513711333275,
0.11375033110380173,
-0.04506459832191467,
0.005224694963544607,
0.028963034972548485,
0.0007449381519109011,
-0.02453286573290825,
0.0354643389582634,
0.038621... | 0.14665 |
# Upgrading !!! important No matter the method you use for upgrading, \_if you use template overrides, make sure your templates are compatible with the new version of ingress-nginx\_. ## Without Helm To upgrade your ingress-nginx installation, it should be enough to change the version of the image in the controller Dep... | null | main | kubernetes-ingress-nginx | [
0.000445258105173707,
0.07246275991201401,
0.08126373589038849,
-0.06574798375368118,
0.06206599622964859,
-0.009215133264660835,
-0.007876724936068058,
0.011159759946167469,
0.019239647313952446,
0.1358836442232132,
0.002835093764588237,
-0.02960491180419922,
-0.0212432648986578,
0.004553... | 0.017211 |
# Bare-metal considerations In traditional \*cloud\* environments, where network load balancers are available on-demand, a single Kubernetes manifest suffices to provide a single point of contact to the Ingress-Nginx Controller to external clients and, indirectly, to any application running inside the cluster. \*Bare-m... | null | main | kubernetes-ingress-nginx | [
-0.12474530935287476,
0.037820469588041306,
0.05622410401701927,
0.03952408581972122,
-0.019670331850647926,
-0.0213596411049366,
0.02264011837542057,
0.022962218150496483,
0.024580780416727066,
0.015520724467933178,
-0.0455186553299427,
-0.08025025576353073,
0.029949570074677467,
-0.07848... | 0.213796 |
[metallb-l2]: https://metallb.universe.tf/concepts/layer2/ [metallb-install]: https://metallb.universe.tf/installation/ [metallb-trafficpolicies]: https://metallb.universe.tf/usage/#traffic-policies ## Over a NodePort Service Due to its simplicity, this is the setup a user will deploy by default when following the step... | null | main | kubernetes-ingress-nginx | [
-0.021537689492106438,
0.0226347167044878,
0.028945790603756905,
-0.03336147218942642,
-0.002798191038891673,
-0.02897556498646736,
0.009088311344385147,
-0.043122291564941406,
0.013979349285364151,
0.003700610250234604,
-0.019137442111968994,
-0.042944394052028656,
0.0033781693782657385,
... | 0.081864 |
default-http-backend-7c5bc89cc9-p86md 1/1 Running 172.17.1.1 host-2 ingress-nginx-controller-cf9ff8c96-8vvf8 1/1 Running 172.17.0.3 host-3 ingress-nginx-controller-cf9ff8c96-pxsds 1/1 Running 172.17.1.4 host-2 ``` Requests sent to `host-2` and `host-3` would be forwarded to NGINX and original client's IP would be prese... | null | main | kubernetes-ingress-nginx | [
-0.09930375218391418,
0.024874035269021988,
0.048387300223112106,
-0.00659023504704237,
0.02485952526330948,
-0.009552493691444397,
0.03943244367837906,
-0.03767964616417885,
0.013258564285933971,
0.07658909261226654,
-0.05112976208329201,
-0.03883300721645355,
0.0521019771695137,
-0.03705... | 0.084284 |
2 replicas, NGINX Pods inherit from the IP address of their host instead of an internal Pod IP. ```console $ kubectl -n ingress-nginx get pod -o wide NAME READY STATUS IP NODE default-http-backend-7c5bc89cc9-p86md 1/1 Running 172.17.1.1 host-2 ingress-nginx-controller-5b4cf5fc6-7lg6c 1/1 Running 203.0.113.3 host-3 ingr... | null | main | kubernetes-ingress-nginx | [
-0.028032472357153893,
-0.005032545421272516,
0.06438403576612473,
-0.0033421386033296585,
-0.010790704749524593,
-0.03961722180247307,
-0.02448209747672081,
-0.07625511288642883,
0.05433906987309456,
0.07712024450302124,
-0.03679685294628143,
-0.041207052767276764,
-0.004504716955125332,
... | 0.136365 |
suitable for private Kubernetes clusters where none of the nodes has a public IP address. On the edge side, the only prerequisite is to dedicate a public IP address that forwards all HTTP traffic to Kubernetes nodes and/or masters. Incoming traffic on TCP ports 80 and 443 is forwarded to the corresponding HTTP and HTTP... | null | main | kubernetes-ingress-nginx | [
-0.026949860155582428,
0.036446597427129745,
0.031272005289793015,
-0.03888370469212532,
-0.039860017597675323,
-0.016570383682847023,
0.023498523980379105,
-0.060821011662483215,
0.0938263013958931,
0.05302411690354347,
-0.00533277727663517,
-0.030582789331674576,
0.012502658180892467,
-0... | 0.109848 |
# Prerequisites Many of the examples in this directory have common prerequisites. ## TLS certificates Unless otherwise mentioned, the TLS secret used in examples is a 2048 bit RSA key/cert pair with an arbitrarily chosen hostname, created as follows ```console $ openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:20... | null | main | kubernetes-ingress-nginx | [
-0.06128612160682678,
0.04889418184757233,
-0.02552863210439682,
-0.007168006617575884,
-0.03393147513270378,
-0.013609590008854866,
-0.052180539816617966,
-0.01550145074725151,
0.09736897796392441,
0.02374936453998089,
-0.015965566039085388,
-0.04643864557147026,
0.05308413878083229,
0.02... | 0.033092 |
# Ingress examples This directory contains a catalog of examples on how to run, configure and scale Ingress. Please review the [prerequisites](PREREQUISITES.md) before trying them. The examples on these pages include the `spec.ingressClassName` field which replaces the deprecated `kubernetes.io/ingress.class: nginx` an... | null | main | kubernetes-ingress-nginx | [
-0.034825846552848816,
0.059307631105184555,
0.06074732169508934,
-0.008992215618491173,
0.020093953236937523,
0.009086359292268753,
-0.05491100251674652,
0.05176123231649399,
-0.0010864182841032743,
0.08864961564540863,
-0.04185539484024048,
-0.07155122607946396,
-0.011515225283801556,
0.... | 0.142807 |
# Rewrite This example demonstrates how to use `Rewrite` annotations. ## Prerequisites You will need to make sure your Ingress targets exactly one Ingress controller by specifying the [ingress.class annotation](../../user-guide/multiple-ingress.md), and that you have an ingress controller [running](../../deploy/index.m... | null | main | kubernetes-ingress-nginx | [
0.0354069247841835,
0.05124300718307495,
0.05368640646338463,
0.02969154715538025,
-0.02260301262140274,
-0.015410074964165688,
0.026842614635825157,
-0.04696943610906601,
0.05076141282916069,
0.07882626354694366,
-0.05257076770067215,
-0.09128069877624512,
0.03447982296347618,
0.010710085... | 0.114103 |
# Multi TLS certificate termination This example uses 2 different certificates to terminate SSL for 2 hostnames. 1. Create tls secrets for foo.bar.com and bar.baz.com as indicated in the yaml 2. Create [multi-tls.yaml](multi-tls.yaml) This should generate a segment like: ```console $ kubectl exec -it ingress-nginx-cont... | null | main | kubernetes-ingress-nginx | [
-0.03295516595244408,
0.0744187980890274,
0.015578866936266422,
-0.05889641121029854,
-0.09917810559272766,
-0.08166827261447906,
-0.0053678592666983604,
-0.061620768159627914,
0.10684247314929962,
0.005674590356647968,
-0.049189187586307526,
-0.10798922926187515,
0.027674958109855652,
0.0... | 0.019453 |
# Canary Ingress Nginx Has the ability to handle canary routing by setting specific annotations, the following is an example of how to configure a canary deployment with weighted canary routing. ## Create your main deployment and service This is the main deployment of your application with the service that will be used... | null | main | kubernetes-ingress-nginx | [
0.04234843701124191,
0.052560631185770035,
0.006621849723160267,
-0.007792121730744839,
-0.039111312478780746,
-0.053005512803792953,
-0.04368198290467262,
-0.0049950843676924706,
-0.023888150230050087,
0.031278450042009354,
-0.07340149581432343,
-0.04936094582080841,
-0.058560293167829514,
... | 0.095293 |
working as expected: ```bash Hostname: production-5c5f65d859-phqzc Hostname: canary-6697778457-zkfjf Hostname: canary-6697778457-zkfjf Hostname: production-5c5f65d859-phqzc Hostname: canary-6697778457-zkfjf Hostname: production-5c5f65d859-phqzc Hostname: production-5c5f65d859-phqzc Hostname: production-5c5f65d859-phqzc... | null | main | kubernetes-ingress-nginx | [
0.06841284036636353,
0.04275389760732651,
-0.015103340148925781,
-0.041289545595645905,
0.02162119187414646,
-0.05840083211660385,
0.013313588686287403,
-0.09585285186767578,
0.031039126217365265,
0.051301125437021255,
0.014850842766463757,
-0.0803741067647934,
0.005450412165373564,
0.0286... | -0.059837 |
# Configuration Snippets ## Ingress The Ingress in [this example](ingress.yaml) adds a custom header to Nginx configuration that only applies to that specific Ingress. If you want to add headers that apply globally to all Ingresses, please have a look at [an example of specifying custom headers](../custom-headers/READM... | null | main | kubernetes-ingress-nginx | [
-0.007010378874838352,
0.1010606661438942,
0.06452378630638123,
-0.035377755761146545,
0.045766692608594894,
0.012077556923031807,
0.047404803335666656,
-0.02021331526339054,
0.09128882735967636,
0.0512552447617054,
-0.08558651804924011,
-0.12112587690353394,
0.004703613463789225,
-0.02131... | 0.136514 |
# Accommodation for JWT JWT (short for Json Web Token) is an authentication method widely used. Basically an authentication server generates a JWT and you then use this token in every request you make to a backend service. The JWT can be quite big and is present in every http headers. This means you may have to adapt t... | null | main | kubernetes-ingress-nginx | [
-0.06220947578549385,
0.06923944503068924,
0.07194510102272034,
-0.0420130118727684,
-0.03298484906554222,
-0.05129428207874298,
-0.015646683052182198,
0.06887263059616089,
-0.015950798988342285,
0.06792493909597397,
-0.10630369931459427,
-0.027402888983488083,
0.03059164248406887,
-0.0399... | 0.100848 |
# Custom Configuration Using a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) is possible to customize the NGINX configuration For example, if we want to change the timeouts we need to create a ConfigMap: ``` $ cat configmap.yaml apiVersion: v1 data: proxy-connect-timeout... | null | main | kubernetes-ingress-nginx | [
-0.008595342747867107,
0.0510106235742569,
0.058936357498168945,
0.014922285452485085,
-0.06226317584514618,
0.006471717264503241,
-0.02097053825855255,
-0.021248599514365196,
0.040253423154354095,
0.07657577097415924,
-0.05383891612291336,
0.00457875756546855,
-0.009504842571914196,
-0.03... | 0.101227 |
# Custom DH parameters for perfect forward secrecy This example aims to demonstrate the deployment of an Ingress-Nginx Controller and use a ConfigMap to configure a custom Diffie-Hellman parameters file to help with "Perfect Forward Secrecy". ## Custom configuration ```console $ cat configmap.yaml apiVersion: v1 data: ... | null | main | kubernetes-ingress-nginx | [
-0.046749867498874664,
0.07002180814743042,
0.006570814643055201,
0.00945805013179779,
-0.025595150887966156,
-0.03159303963184357,
0.01584804430603981,
-0.0021771653555333614,
0.04296332970261574,
0.04964124411344528,
0.01947190798819065,
-0.08374875038862228,
0.005358920432627201,
-0.029... | 0.039418 |
# Sysctl tuning This example aims to demonstrate the use of an Init Container to adjust sysctl default values using `kubectl patch`. ```console kubectl patch deployment -n ingress-nginx ingress-nginx-controller \ --patch="$(curl https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/docs/examples/customization... | null | main | kubernetes-ingress-nginx | [
-0.04253901168704033,
0.04392767697572708,
0.02843153290450573,
-0.002597078448161483,
-0.01959233172237873,
-0.07508967816829681,
0.009935244917869568,
0.003754651639610529,
0.004413919989019632,
0.07865244895219803,
-0.04216049611568451,
-0.006871986202895641,
0.0028105685487389565,
-0.0... | 0.115319 |
# External authentication, authentication service response headers propagation This example demonstrates propagation of selected authentication service response headers to a backend service. Sample configuration includes: \* Sample authentication service producing several response headers \* Authentication logic is bas... | null | main | kubernetes-ingress-nginx | [
-0.015269309282302856,
0.024062320590019226,
-0.06012176349759102,
-0.0834774374961853,
-0.025403980165719986,
-0.018824024125933647,
0.049503572285175323,
-0.0057788509875535965,
0.07823704928159714,
0.057865407317876816,
0.04742756858468056,
-0.13514509797096252,
0.0470866821706295,
-0.0... | 0.086774 |
# Custom Errors This example demonstrates how to use a custom backend to render custom error pages. If you are using the Helm Chart, look at [example values](https://github.com/kubernetes/ingress-nginx/blob/main/docs/examples/customization/custom-errors/custom-default-backend.helm.values.yaml) and don't forget to add t... | null | main | kubernetes-ingress-nginx | [
0.001349492697045207,
0.06252731382846832,
0.09500375390052795,
-0.0069017838686704636,
0.0007480038329958916,
0.03248898312449455,
-0.0413513109087944,
0.06367985159158707,
0.006084890570491552,
0.10366977006196976,
-0.047590434551239014,
-0.053914040327072144,
0.06608577072620392,
-0.046... | 0.051699 |
to `return 503;`, to make the NGINX Ingress Controller always return the 503 HTTP error page for all the requests | null | main | kubernetes-ingress-nginx | [
-0.06243224814534187,
0.08205489814281464,
0.01038726419210434,
-0.022637953981757164,
0.010416997596621513,
-0.05184110626578331,
-0.025356724858283997,
-0.04523774981498718,
0.044410400092601776,
0.1440918892621994,
-0.004407584201544523,
-0.05671565607190132,
0.0007675262750126421,
-0.0... | 0.024258 |
# Custom Headers ## Caveats Changes to the custom header config maps do not force a reload of the ingress-nginx-controllers. ### Workaround To work around this limitation, perform a rolling restart of the deployment. ## Example This example demonstrates configuration of the Ingress-Nginx Controller via a ConfigMap to p... | null | main | kubernetes-ingress-nginx | [
-0.03284170851111412,
0.08415326476097107,
0.08780966699123383,
-0.022526197135448456,
-0.023281551897525787,
0.013589256443083286,
0.003285192884504795,
0.009642161428928375,
0.020096775144338608,
0.08654523640871048,
-0.030794216319918633,
-0.08083748817443848,
0.01634511724114418,
-0.02... | 0.068098 |
# OpenPolicyAgent and pathType enforcing Ingress API allows users to specify different [pathType](https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types) on Ingress object. While pathType `Exact` and `Prefix` should allow only a small set of characters, pathType `ImplementationSpecific` allows any ... | null | main | kubernetes-ingress-nginx | [
-0.058847181499004364,
0.007016838062554598,
0.018694816157221794,
-0.0034985137172043324,
-0.02309517189860344,
-0.010701007209718227,
0.06150020658969879,
-0.024750251322984695,
0.06360504776239395,
0.05016756057739258,
0.009077183902263641,
-0.018114207312464714,
0.0033636335283517838,
... | 0.184785 |
# Static IPs This example demonstrates how to assign a static-ip to an Ingress on through the Ingress-NGINX controller. ## Prerequisites You need a [TLS cert](../PREREQUISITES.md#tls-certificates) and a [test HTTP service](../PREREQUISITES.md#test-http-service) for this example. You will also need to make sure your Ing... | null | main | kubernetes-ingress-nginx | [
-0.0767587423324585,
0.02366495132446289,
0.03361274302005768,
0.008379065431654453,
-0.012375387363135815,
-0.002602779073640704,
0.06081218272447586,
-0.07716385275125504,
-0.0020283167250454426,
0.08054820448160172,
0.0033509728964418173,
-0.08016175776720047,
0.08022776246070862,
-0.04... | 0.079995 |
# gRPC This example demonstrates how to route traffic to a gRPC service through the Ingress-NGINX controller. ## Prerequisites 1. You have a kubernetes cluster running. 2. You have a domain name such as `example.com` that is configured to route traffic to the Ingress-NGINX controller. 3. You have the ingress-nginx-cont... | null | main | kubernetes-ingress-nginx | [
-0.020629875361919403,
0.010525941848754883,
-0.026163917034864426,
-0.03293367102742195,
-0.08882956206798553,
-0.010623749345541,
0.05311312526464462,
-0.012574727647006512,
0.0658067986369133,
0.05608795955777168,
-0.05723066255450249,
-0.10600673407316208,
-0.004785172175616026,
0.0711... | 0.084393 |
# External Basic Authentication ### Example 1 Use an external service (Basic Auth) located in `https://httpbin.org` ``` $ kubectl create -f ingress.yaml ingress "external-auth" created $ kubectl get ing external-auth NAME HOSTS ADDRESS PORTS AGE external-auth external-auth-01.sample.com 172.17.4.99 80 13s $ kubectl get... | null | main | kubernetes-ingress-nginx | [
-0.04034440591931343,
0.046764615923166275,
-0.005645529367029667,
-0.03132931515574455,
-0.007969966158270836,
-0.04178331419825554,
0.00550901610404253,
0.017362505197525024,
0.07533898949623108,
0.06530992686748505,
-0.027836525812745094,
-0.11629095673561096,
0.00964093953371048,
0.013... | 0.140005 |
# External OAUTH Authentication ### Overview The `auth-url` and `auth-signin` annotations allow you to use an external authentication provider to protect your Ingress resources. !!! Important This annotation requires `ingress-nginx-controller v0.9.0` or greater. ### Key Detail This functionality is enabled by deploying... | null | main | kubernetes-ingress-nginx | [
-0.05267592892050743,
0.0791315883398056,
-0.01992388255894184,
-0.005119160749018192,
0.022046439349651337,
-0.034086842089891434,
0.05650218948721886,
0.02867412008345127,
0.05863749235868454,
0.04692621901631355,
-0.04033776745200157,
-0.06916137784719467,
0.053222306072711945,
0.013691... | 0.150598 |
# Client Certificate Authentication It is possible to enable Client-Certificate Authentication by adding additional annotations to your Ingress Resource. Before getting started you must have the following Certificates configured: 1. CA certificate and Key (Intermediate Certs need to be in CA) 2. Server Certificate (Sig... | null | main | kubernetes-ingress-nginx | [
-0.029433559626340866,
0.053203266113996506,
-0.05347063019871712,
-0.034783985465765,
-0.020291713997721672,
-0.005119768902659416,
0.015197993256151676,
0.08820498734712601,
0.02672085165977478,
0.007027770858258009,
-0.05151905119419098,
-0.11631213873624802,
0.1408243328332901,
0.06799... | 0.001421 |
# Basic Authentication This example shows how to add authentication in a Ingress rule using a secret that contains a file generated with `htpasswd`. It's important the file generated is named `auth` (actually - that the secret has a key `data.auth`), otherwise the ingress-controller returns a 503. ## Create htpasswd fi... | null | main | kubernetes-ingress-nginx | [
-0.0390070304274559,
0.06891632080078125,
-0.05002739280462265,
-0.04222170636057854,
0.00016548539861105382,
0.008535400032997131,
0.04131374880671501,
0.024939976632595062,
0.08557616919279099,
0.08974014222621918,
0.024692345410585403,
-0.09227745234966278,
0.04502721503376961,
-0.06000... | 0.086528 |
# Sticky sessions This example demonstrates how to achieve session affinity using cookies. ## Deployment Session affinity can be configured using the following annotations: |Name|Description|Value| | --- | --- | --- | |nginx.ingress.kubernetes.io/affinity|Type of the affinity, set this to `cookie` to enable session aff... | null | main | kubernetes-ingress-nginx | [
-0.020043959841132164,
0.022623566910624504,
-0.0017788633704185486,
0.027811499312520027,
-0.03922772407531738,
-0.0635431781411171,
0.07802751660346985,
-0.01105023268610239,
-0.01028812862932682,
0.013778792694211006,
-0.02399226650595665,
-0.014399770647287369,
-0.021039795130491257,
0... | 0.124281 |
configuration, the first created Ingress will be used. This means that you can face the situation that you've configured session affinity on one Ingress and it doesn't work because the Service is pointing to another Ingress that doesn't configure this. [ingress-paths]: ../../../user-guide/ingress-path-matching.md [cons... | null | main | kubernetes-ingress-nginx | [
-0.02819906547665596,
-0.02368440479040146,
-0.03786397725343704,
-0.045004911720752716,
-0.02705702744424343,
-0.05893285199999809,
0.12576451897621155,
-0.038791365921497345,
0.03724495321512222,
0.004613087512552738,
0.013731160201132298,
0.0015394382644444704,
0.06659002602100372,
0.04... | 0.124107 |
# Docker registry This example demonstrates how to deploy a [docker registry](https://github.com/docker/distribution) in the cluster and configure Ingress to enable access from the Internet. ## Deployment First we deploy the docker registry in the cluster: ```console kubectl apply -f https://raw.githubusercontent.com/k... | null | main | kubernetes-ingress-nginx | [
-0.05955791473388672,
0.05064330995082855,
0.023859690874814987,
-0.03299803286790848,
-0.01939411461353302,
-0.034319911152124405,
0.0002755352761596441,
0.0043959422037005424,
0.05473962798714638,
0.08907365053892136,
-0.027419015765190125,
-0.08498913049697876,
0.030177796259522438,
0.0... | 0.136272 |
# TLS termination This example demonstrates how to terminate TLS through the Ingress-Nginx Controller. ## Prerequisites You need a [TLS cert](../PREREQUISITES.md#tls-certificates) and a [test HTTP service](../PREREQUISITES.md#test-http-service) for this example. ## Deployment Create a `ingress.yaml` file. ```yaml apiVe... | null | main | kubernetes-ingress-nginx | [
-0.06654328107833862,
0.11010245978832245,
0.0022753651719540358,
-0.03177650272846222,
-0.03335551172494888,
-0.06898020207881927,
0.03137655183672905,
-0.04464516416192055,
0.06252195686101913,
0.11155305802822113,
-0.03240470588207245,
-0.059026844799518585,
0.021920815110206604,
0.0265... | 0.067468 |
# Availability zone aware routing ## Table of Contents - [Availability zone aware routing](#availability-zone-aware-routing) - [Table of Contents](#table-of-contents) - [Summary](#summary) - [Motivation](#motivation) - [Goals](#goals) - [Non-Goals](#non-goals) - [Proposal](#proposal) - [Implementation History](#impleme... | null | main | kubernetes-ingress-nginx | [
-0.024422163143754005,
-0.019102906808257103,
0.016766555607318878,
0.014709153212606907,
0.052775800228118896,
0.002292625606060028,
-0.002330888994038105,
-0.004772614687681198,
0.04233092442154884,
0.05251745507121086,
-0.10382746160030365,
-0.027599230408668518,
0.011914772912859917,
-... | 0.19824 |
from the map in memory and store it as a field on the endpoint. \_\_This solution assumes `failure-domain.beta.kubernetes.io/zone`\_\_ annotation does not change until the end of the node's life. Otherwise, we have to watch update events as well on the nodes and that'll add even more overhead. Alternatively, we can get... | null | main | kubernetes-ingress-nginx | [
0.05517018958926201,
0.017072876915335655,
0.019743764773011208,
0.01279410906136036,
0.07538040727376938,
-0.003107961732894182,
0.020060161128640175,
-0.021902641281485558,
0.114013671875,
0.03167172148823738,
-0.04951479658484459,
-0.05825949087738991,
-0.03606070205569267,
-0.084257602... | 0.143549 |
# Proposal to split containers \* All the NGINX files should live on one container \* No file other than NGINX files should exist on this container \* This includes not mounting the service account \* All the controller files should live on a different container \* Controller container should have bare minimum to work ... | null | main | kubernetes-ingress-nginx | [
-0.08871787041425705,
0.0032024052925407887,
-0.04346594586968422,
-0.04399733990430832,
0.004406537860631943,
-0.013620046898722649,
0.012243373319506645,
0.04735300689935684,
-0.0731414407491684,
0.003203806234523654,
0.014671663753688335,
-0.03928066045045853,
-0.02956506237387657,
0.03... | -0.049337 |
www-data 5349 Jun 23 19:44 mime.types.default drwxr-xr-x 2 www-data www-data 4096 Jun 23 19:44 modsecurity drwxr-xr-x 2 www-data www-data 4096 Jun 23 19:44 modules -rw-r--r-- 1 www-data www-data 18275 Oct 1 21:28 nginx.conf -rw-r--r-- 1 www-data www-data 2656 Jun 23 19:44 nginx.conf.default -rwx------ 1 www-data www-da... | null | main | kubernetes-ingress-nginx | [
-0.08948564529418945,
0.05481184273958206,
-0.07432081550359726,
-0.01368478313088417,
0.09326110780239105,
-0.09823142737150192,
-0.02160373516380787,
-0.03302974998950958,
0.017375504598021507,
0.012951716780662537,
0.07973648607730865,
0.009173120371997356,
0.056987058371305466,
0.03346... | 0.050793 |
# Remove static SSL configuration mode ## Table of Contents - [Summary](#summary) - [Motivation](#motivation) - [Goals](#goals) - [Non-Goals](#non-goals) - [Proposal](#proposal) - [Implementation Details/Notes/Constraints](#implementation-detailsnotesconstraints) - [Drawbacks](#drawbacks) - [Alternatives](#alternatives... | null | main | kubernetes-ingress-nginx | [
-0.05003218352794647,
0.10191576182842255,
0.04527665674686432,
0.048019763082265854,
0.0017830501310527325,
-0.017666954547166824,
-0.008000382222235203,
-0.02306872233748436,
0.0361919142305851,
-0.01141752116382122,
-0.0229084100574255,
-0.0036023652646690607,
0.020425058901309967,
0.07... | 0.062836 |
# Kubernetes Enhancement Proposals (KEPs) A Kubernetes Enhancement Proposal (KEP) is a way to propose, communicate and coordinate on new efforts for the Kubernetes project. For this reason, the `ingress-nginx` project is adopting it. ## Quick start for the KEP process Follow the process outlined in the [KEP template](Y... | null | main | kubernetes-ingress-nginx | [
-0.09145357459783554,
0.048168934881687164,
0.1030547246336937,
-0.0579318143427372,
0.04902167618274689,
-0.010820471681654453,
-0.011459624394774437,
-0.05156996473670006,
0.044423121958971024,
0.04848421737551689,
-0.07147534936666489,
-0.06074875593185425,
-0.034161172807216644,
-0.011... | 0.200358 |
# Title This is the title of the KEP. Keep it simple and descriptive. A good title can help communicate what the KEP is and should be considered as part of any review. The title should be lowercased and spaces/punctuation should be replaced with `-`. To get started with this template: 1. \*\*Make a copy of this templat... | null | main | kubernetes-ingress-nginx | [
-0.06991018354892731,
0.14223633706569672,
0.06347537785768509,
-0.05171864852309227,
-0.0019241764675825834,
0.04708117991685867,
-0.001815342460758984,
0.012726720422506332,
-0.09050697833299637,
0.025860628113150597,
-0.019924692809581757,
-0.06451646238565445,
0.0018713376484811306,
-0... | 0.113931 |
the things that people will be able to do if this KEP is implemented. Include as much detail as possible so that people can understand the "how" of the system. The goal here is to make this feel real for users without getting bogged down. #### Story 1 #### Story 2 ### Implementation Details/Notes/Constraints [optional]... | null | main | kubernetes-ingress-nginx | [
-0.039968930184841156,
0.1004980280995369,
0.11347176134586334,
-0.08111210912466049,
-0.014206109568476677,
0.011074705049395561,
-0.009375018998980522,
0.034646350890398026,
-0.04792289808392525,
0.022088320925831795,
-0.040794387459754944,
-0.05444280430674553,
-0.01346980594098568,
-0.... | 0.181947 |
# Ingress NGINX - Code Overview This document provides an overview of Ingress NGINX code. ## Core Golang code This part of the code is responsible for the main logic of Ingress NGINX. It contains all the logics that parses [Ingress Objects](https://kubernetes.io/docs/concepts/services-networking/ingress/), [annotations... | null | main | kubernetes-ingress-nginx | [
-0.05814354494214058,
0.023868946358561516,
0.04210592806339264,
0.013132086023688316,
0.02536623924970627,
-0.021882297471165657,
0.028062809258699417,
-0.062103502452373505,
0.09031684696674347,
0.024823660030961037,
-0.02317957580089569,
-0.015921518206596375,
0.018084557726979256,
-0.0... | 0.23448 |
kubectl plugin It contains kubectl plugin for inspecting your ingress-nginx deployments. This part of code can be found in [cmd/plugin](https://github.com/kubernetes/ingress-nginx/tree/main/cmd/plugin) directory Detail functions flow and available flow can be found in [kubectl-plugin](https://github.com/kubernetes/ingr... | null | main | kubernetes-ingress-nginx | [
-0.06847695261240005,
0.05289166793227196,
0.017885472625494003,
-0.024768078699707985,
0.03290858119726181,
0.005897598806768656,
-0.01988743618130684,
-0.012780679389834404,
0.09372325986623764,
0.07433400303125381,
0.005459424573928118,
-0.04806813597679138,
-0.028220603242516518,
-0.04... | 0.185878 |
Developing for Ingress-Nginx Controller This document explains how to get started with developing for Ingress-Nginx Controller. For the really new contributors, who want to contribute to the INGRESS-NGINX project, but need help with understanding some basic concepts, that are needed to work with the Kubernetes ingress ... | null | main | kubernetes-ingress-nginx | [
-0.05609467253088951,
0.0569368451833725,
0.009625105187296867,
-0.011367419734597206,
-0.0027232025749981403,
-0.03227215260267258,
0.06776492297649384,
-0.013800053857266903,
0.04458841681480408,
0.05438007786870003,
0.005054667592048645,
-0.029451915994286537,
-0.01543839368969202,
-0.0... | 0.188348 |
# Mocking in kubectl-ai ## Gomock developer workflow We use [gomock](https://github.com/uber-go/mock) to mock external dependencies. All mocks and generated files live under `internal/mocks/`. - \*\*Everyday commands\*\* - Regenerate mocks after changing interfaces or adding new ones: `make generate` - Verify nothing i... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/mocking.md | main | kubectl-ai | [
-0.03711624816060066,
-0.02989896945655346,
0.007772571407258511,
-0.04655222222208977,
-0.036745376884937286,
-0.04608903080224991,
-0.03657601773738861,
-0.0632045790553093,
0.002540258225053549,
0.005907797254621983,
0.028465284034609795,
-0.08485730737447739,
-0.016950828954577446,
-0.... | 0.10927 |
# kubectl-ai MCP Client Integration ## Multi-Server Orchestration for Security Automation The MCP (Model Context Protocol) Client feature enables kubectl-ai to coordinate multiple specialized tools through natural language commands. This integration demonstrates automated security workflows that combine RBAC scanning w... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/mcp-client.md | main | kubectl-ai | [
-0.030838724225759506,
-0.017323816195130348,
-0.01276693306863308,
-0.021857233718037605,
0.008182941004633904,
-0.022677864879369736,
0.034500058740377426,
-0.01699194684624672,
0.08591510355472565,
0.04145798087120056,
-0.05617658421397209,
-0.08414410799741745,
0.07634449750185013,
-0.... | 0.264544 |
security audit processes - \*\*Consistency\*\*: Standardized security scanning and reporting - \*\*Extensibility\*\*: Modular architecture supports additional integrations - \*\*Efficiency\*\*: Rapid security assessment and stakeholder notification | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/mcp-client.md | main | kubectl-ai | [
-0.03895825520157814,
0.026451699435710907,
-0.09519331902265549,
-0.009495152160525322,
0.05613631010055542,
-0.0033635981380939484,
0.0939718708395958,
-0.02464170567691326,
0.025304481387138367,
-0.03178149834275246,
0.018482424318790436,
-0.02539568394422531,
0.041796255856752396,
0.03... | 0.295226 |
# AWS Bedrock Provider kubectl-ai supports AWS Bedrock models including Claude Sonnet 4 and Claude 3.7. ## Setup ### AWS Credentials Configure AWS credentials using standard AWS SDK methods: ```bash # Option 1: Environment variables export AWS\_ACCESS\_KEY\_ID="your-access-key" export AWS\_SECRET\_ACCESS\_KEY="your-sec... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/bedrock.md | main | kubectl-ai | [
0.057709161192178726,
0.015879468992352486,
-0.06231939047574997,
-0.051535192877054214,
0.038495954126119614,
-0.023730484768748283,
-0.002047371817752719,
-0.02985692396759987,
0.027417974546551704,
0.04564409330487251,
-0.038954317569732666,
-0.1192818135023117,
0.019382178783416748,
0.... | 0.000531 |
# kubectl-ai MCP Server kubectl-ai can run as an MCP (Model Context Protocol) server, exposing kubectl-ai tools to other MCP clients. The server can run in two modes: 1. \*\*Built-in tools only\*\*: Exposes only kubectl-ai's native tools 2. \*\*External tool discovery\*\*: Additionally discovers and exposes tools from ... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/mcp-server.md | main | kubectl-ai | [
-0.019694671034812927,
-0.0536128394305706,
0.021131740882992744,
-0.035351935774087906,
-0.010483809746801853,
-0.02768213301897049,
-0.03872714936733246,
-0.00992554146796465,
0.05473392829298973,
0.030889585614204407,
-0.014852347783744335,
-0.07814103364944458,
0.0020285993814468384,
-... | 0.204444 |
Server │───▶│ External Tools │ │ (Claude, etc.) │ │ │ │ (filesystem, │ │ │ │ ┌───────────────┐ │ │ web search, │ │ │ │ │ Built-in │ │ │ etc.) │ │ │ │ │ kubectl tools │ │ │ │ │ │ │ └───────────────┘ │ │ │ └─────────────────┘ └───────────────────┘ └─────────────────┘ ``` The kubectl-ai MCP server acts as both: - An \*\*M... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/mcp-server.md | main | kubectl-ai | [
-0.030372384935617447,
-0.09181495010852814,
0.10057879984378815,
-0.014309518970549107,
-0.007657452952116728,
-0.03274368494749069,
-0.07540754973888397,
-0.039504338055849075,
0.0855053961277008,
0.053846996277570724,
0.004202960059046745,
-0.07892143726348877,
0.005959299858659506,
-0.... | 0.136664 |
# Deploying k8-kate to Google Kubernetes Engine ## Prerequisites - A GKE cluster (Standard or Autopilot). - `gcloud` CLI authenticated with `gcloud auth login`. - Local Docker environment (or Cloud Build) capable of building and pushing container images. - [`kubectl` configured](https://cloud.google.com/kubernetes-engi... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/gke-deployment.md | main | kubectl-ai | [
-0.019300304353237152,
-0.009127922356128693,
0.05962110683321953,
-0.044824711978435516,
-0.026999464258551598,
0.0010749625507742167,
-0.03177132084965706,
0.0021712156012654305,
0.01387719251215458,
0.07550819218158722,
-0.04669026657938957,
-0.11327772587537766,
0.03521547093987465,
-0... | 0.001215 |
repository or pushed image, delete them using `gcloud artifacts repositories delete` and `gcloud artifacts docker images delete`. | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/gke-deployment.md | main | kubectl-ai | [
-0.036671124398708344,
0.049507588148117065,
0.06419940292835236,
-0.046686384826898575,
0.056511253118515015,
-0.1368241161108017,
-0.03617464751005173,
-0.10197361558675766,
0.06030659005045891,
0.03044089861214161,
0.06997821480035782,
0.018848415464162827,
0.05192670598626137,
0.027494... | -0.082107 |
# Custom Tools for kubectl-ai `kubectl-ai` leverages LLMs to suggest and execute Kubernetes operations using a set of powerful tools. It comes with built-in tools like `kubectl` and `bash`. The `kubectl-ai` assistant can be extended with custom tools to interact with various command-line interfaces (CLIs) beyond `kubec... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/tools.md | main | kubectl-ai | [
0.0032527318689972162,
-0.021861078217625618,
0.0022843964397907257,
-0.03386617824435234,
-0.041552621871232986,
-0.016816994175314903,
-0.013864661566913128,
0.002328505041077733,
0.08183415979146957,
0.06316569447517395,
-0.04059236869215965,
-0.11756811290979385,
0.010501069948077202,
... | 0.221929 |
\ your-kubectl-ai-image:latest \ --custom-tools-config=/my-custom-tools \ "your prompt here" ``` ## Sample Custom Tools The following sample custom tools are configured by default. | Tool | Description | YAML File | | :--------------------------------------------------------- | :----------------------------------------... | https://github.com/GoogleCloudPlatform/kubectl-ai/blob/main/docs/tools.md | main | kubectl-ai | [
0.022990580648183823,
0.03575744107365608,
-0.02437298558652401,
-0.05212795361876488,
-0.06234022602438927,
-0.01589886099100113,
-0.0020628052297979593,
0.00595824234187603,
0.08734326809644699,
0.05698077008128166,
0.03876323625445366,
-0.1409374624490738,
-0.01641600951552391,
-0.09193... | 0.103299 |
# Helm 4 Overview Helm v4 represents a significant evolution from v3, introducing breaking changes, new architectural patterns, and enhanced functionality while maintaining backwards compatibility for charts. For more information about the planned Helm 4 release phases, see [Path to Helm v4](https://helm.sh/blog/path-t... | https://github.com/helm/helm-www/blob/main/docs/overview.md | main | helm | [
0.019372086971998215,
0.08121636509895325,
0.057621296495199203,
-0.06672202050685883,
0.1043972447514534,
-0.004559780936688185,
-0.11751911789178848,
0.033705759793519974,
-0.023335164412856102,
0.05415298417210579,
0.021924450993537903,
0.016571618616580963,
-0.041455525904893875,
-0.04... | 0.153896 |
Faster dependency resolution and new content-based chart caching. #### Error Messages Clearer, more helpful error output. #### Registry Authentication Better OAuth and token support for private registries. #### CLI Flags renamed Some common CLI flags are renamed to better clarify their operation. The existing flags rem... | https://github.com/helm/helm-www/blob/main/docs/overview.md | main | helm | [
-0.008956851437687874,
0.07027929276227951,
0.08676845580339432,
-0.06711644679307938,
0.10769759863615036,
-0.02116972766816616,
-0.1030886322259903,
-0.028830956667661667,
0.011013115756213665,
0.006127172149717808,
0.02692459151148796,
0.021060988306999207,
-0.021469004452228546,
-0.016... | -0.000883 |
# Helm 4 Full Changelog \*\*Scope\*\*: 443 PRs from (`v4.2.0`) compared to `v3.19.0` \*\*v4-only\*\*: 407 PRs (36 backported to v3 excluded) See the [Overview](/overview.md) for an actionable summary of these changes. ## New Features New features in Helm 4 that were not backported to v3 | PR | Date | Author | Title | |... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
0.01254128385335207,
0.01264182012528181,
0.04121353477239609,
-0.045924682170152664,
0.07399594783782959,
0.05912528559565544,
-0.11753706634044647,
-0.027599120512604713,
-0.009235365316271782,
0.04448900744318962,
0.034666676074266434,
-0.031067539006471634,
-0.06379251927137375,
-0.060... | -0.000904 |
2025-08-21 | gjenkins8 | BREAKING CHANGE: [HIP-0026] Move pkg/plugin -> internal/plugin | | #31030 | 2025-08-14 | gjenkins8 | BREAKING CHANGE: HIP-0023: Kube client support server-side apply | | #12624 | 2025-08-13 | papdaniel | show crds command output separated by document separator | | #13111 | 2025-08-13 | rawtaz |... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.08151043951511383,
-0.002070107962936163,
-0.03855648264288902,
-0.09283647686243057,
-0.04521743580698967,
0.023189956322312355,
-0.04640364646911621,
0.02968529798090458,
0.015074118040502071,
0.026513002812862396,
0.021419992670416832,
-0.0751650407910347,
0.0238184854388237,
-0.0580... | 0.02979 |
can be empty | | #31128 | 2026-02-11 | orgads | fix(downloader): prevent concurrent file access errors on Windows | | #31772 | 2026-01-29 | matheuscscp | Revert "Consider GroupVersionKind when matching resources" | | #31751 | 2026-01-28 | tamcore | fix(copystructure): handle nil elements in slice copying | | #31717 | 2... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.06593318283557892,
-0.035388994961977005,
-0.02175600454211235,
-0.014245339669287205,
0.0013202487025409937,
-0.038837261497974396,
0.005601427052170038,
-0.023130988702178,
0.06406491994857788,
0.048093196004629135,
0.04674570634961128,
-0.10053741931915283,
-0.007010394707322121,
-0.... | 0.201659 |
| 2025-10-02 | TerryHowe | fix: Ignore absolute path when RepoUrl is provided | | #31334 | 2025-09-30 | fleaz | Fix typo in bug-report issue template | | #31330 | 2025-09-25 | mattfarina | Restore lint rule for excluding meaningless name | | #31320 | 2025-09-25 | kosiew | provenance: allow RSA signing when ed25519 keys... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.05205252394080162,
0.010746719315648079,
0.012548577971756458,
-0.04127379134297371,
0.1115410178899765,
0.006060001906007528,
-0.007100271992385387,
0.043403349816799164,
-0.032511793076992035,
0.03779773786664009,
0.06513144820928574,
-0.06850650906562805,
0.026436666026711464,
-0.027... | -0.048749 |
| | #30803 | 2025-04-25 | mattfarina | Fixing windows build | | #30783 | 2025-04-23 | rpolishchuk | fix: chart icon presence test | | #30777 | 2025-04-23 | ryanhockstad | fix: null merge | | #9175 | 2025-04-23 | dastrobu | fix: copy dependencies on aliasing to avoid sharing chart references on multiply aliased dependen... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.013239037245512009,
-0.015222379006445408,
0.007425226271152496,
-0.05403480306267738,
0.046895112842321396,
0.006036793813109398,
-0.05839477851986885,
0.06752098351716995,
-0.05327252671122551,
0.02289542555809021,
0.0506020225584507,
-0.08345029503107071,
0.006726609542965889,
-0.034... | 0.028088 |
mmorel-35 | refactor(cmd): errorlint linter | | #31809 | 2026-02-10 | mmorel-35 | refactor(pkg): errorlint linter | | #31698 | 2026-01-08 | sarfraj89 | Lint sync-repo.sh with ShellCheck | | #31239 | 2026-01-03 | StephanieHhnbrg | Add tests to action package to improve coverage | | #31684 | 2026-01-01 | Skarlso | fix: t... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.07000891119241714,
-0.032872702926397324,
0.01485399715602398,
0.018068840727210045,
0.018199359998106956,
-0.007388151716440916,
0.029214229434728622,
0.08247675001621246,
-0.06843185424804688,
0.13233643770217896,
0.07033821940422058,
-0.07879859209060669,
-0.02036433294415474,
-0.079... | 0.082235 |
| 2025-09-16 | TerryHowe | chore: remove pkg/time which is no longer needed | | #31287 | 2025-09-16 | miledxz | improve fileutil test coverage | | #31292 | 2025-09-16 | reddaisyy | refactor: use strings.builder | | #31286 | 2025-09-12 | yajianggroup | refactor: use strings.CutPrefix | | #31258 | 2025-09-08 | StephanieH... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.07778064161539078,
0.007085110992193222,
0.042237136512994766,
0.027067162096500397,
0.032504186034202576,
0.048609327524900436,
-0.05194546654820442,
0.021918807178735733,
-0.07092823833227158,
0.0498245432972908,
0.07511377334594727,
-0.06240293011069298,
-0.012629913166165352,
-0.038... | -0.082196 |
#30871 | 2025-05-20 | gjenkins8 | Run test OCI registry localhost | | #30866 | 2025-05-20 | mmorel-35 | chore: enable thelper linter | | #30863 | 2025-05-16 | mattfarina | Adding test for list command | | #30850 | 2025-05-12 | yetyear | refactor: use maps.Copy for cleaner map handling | | #30829 | 2025-05-09 | TerryHow... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.07830290496349335,
0.030992818996310234,
0.0000238687644014135,
-0.004406978841871023,
0.0403054803609848,
-0.012315881438553333,
-0.04077528417110443,
0.041279617697000504,
-0.07791399210691452,
0.08589841425418854,
0.11034674197435379,
-0.08779995888471603,
0.025675863027572632,
-0.06... | 0.042311 |
#13611 | 2025-01-07 | mattfarina | BREAKING CHANGE: Updating the internal version to v4 | | #13576 | 2025-01-07 | gjenkins8 | refactor: Consolidate lint package Run() functions | | #13577 | 2025-01-07 | gjenkins8 | refactor: Remove redundant `NewPullWithOpts` | | #13599 | 2025-01-07 | gjenkins8 | cleanup: `ProcessDepen... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.03839988261461258,
0.005928254686295986,
0.012842893600463867,
-0.06300553679466248,
0.089656300842762,
-0.007502255495637655,
-0.06546331942081451,
0.01663692481815815,
0.0006199539639055729,
0.10016711801290512,
0.0707501694560051,
-0.006664990447461605,
-0.05916426703333855,
-0.09479... | 0.028286 |
TerryHowe | pkg/kube: remove legacy import comments from test files | | #31931 | 2026-03-12 | abhay1999 | pkg/kube: remove legacy import comments | | #31921 | 2026-03-11 | tsinglua | chore: fix some minor issues in the comments | | #31898 | 2026-03-09 | TerryHowe | fix: bump go.opentelemetry.io/otel/sdk to v1.40.0 for ... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.0778680071234703,
-0.05793348699808121,
0.004873210098594427,
-0.02054394781589508,
0.03305909037590027,
0.011759343557059765,
-0.03078373894095421,
0.05082220211625099,
-0.05604434758424759,
0.018502382561564445,
0.07458687573671341,
-0.031483765691518784,
-0.024625441059470177,
-0.005... | 0.083356 |
#31503 | 2025-11-14 | crenshaw-dev | docs: Fix LFX Health Score badge URL in README.md | | #31488 | 2025-11-12 | gjenkins8 | Publish Helm v4 -> `helm-latest-version` | | #31485 | 2025-11-12 | mattfarina | Adding script to download Helm v4 | | #31318 | 2025-11-12 | gjenkins8 | fix: Helm v4 release distribution & `get-he... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.030734099447727203,
0.020409539341926575,
-0.04448322951793671,
-0.09707070142030716,
0.06435426324605942,
0.04282868653535843,
-0.010460253804922104,
0.023308565840125084,
-0.027669506147503853,
0.03263262286782265,
0.05822060629725456,
-0.04908369481563568,
0.04669078812003136,
-0.041... | 0.011001 |
| #13443 | 2024-11-15 | mattfarina | Updating docs around v3 and v4 | ## v4 Changes Also Backported to v3 These PRs were included in v4 but were also backported to v3 releases ### New Features (Backported) | PR | Date | Author | Title | |---|---|---|---| | #30696 | 2025-03-24 | benoittgt | Inform about time spent waiti... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
0.00240455218590796,
-0.01520044356584549,
-0.05130831524729729,
-0.026266027241945267,
0.0027863632421940565,
0.005353644024580717,
-0.12219259142875671,
0.03827694058418274,
-0.02361978031694889,
0.01904660277068615,
-0.0016953371232375503,
-0.01433410681784153,
-0.03515126183629036,
-0.... | 0.049891 |
| TerryHowe | chore(oci): migrate to ORAS Golang library v2 | | #13546 | 2024-12-19 | mattfarina | Update to Go 1.23 | | #13499 | 2024-12-06 | gjenkins8 | Shadow ORAS remote.Client interface | ### Other (Backported) | PR | Date | Author | Title | |---|---|---|---| | #32152 | 2026-05-27 | TerryHowe | fix(deps): bump gol... | https://github.com/helm/helm-www/blob/main/docs/changelog.md | main | helm | [
-0.0759347453713417,
0.005321019794791937,
-0.012054773047566414,
-0.06272806972265244,
-0.00006372282223310322,
0.006559306290000677,
-0.04475107416510582,
0.03741466999053955,
-0.020300859585404396,
0.027181420475244522,
0.06644250452518463,
-0.08901521563529968,
-0.023421047255396843,
0... | 0.04506 |
This guide covers how you can quickly get started using Helm. ## Prerequisites The following prerequisites are required for a successful and properly secured use of Helm. 1. A Kubernetes cluster 2. Deciding what security configurations to apply to your installation, if any 3. Installing and configuring Helm. ### Instal... | https://github.com/helm/helm-www/blob/main/docs/intro/quickstart.md | main | helm | [
0.045351799577474594,
0.03391338139772415,
0.05031687021255493,
-0.08876898884773254,
0.021194959059357643,
0.051013313233852386,
-0.0865422934293747,
0.040229640901088715,
0.031569961458444595,
0.06149730458855629,
-0.02268981747329235,
-0.05315621942281723,
0.00373472785577178,
-0.048478... | 0.039642 |
more about the available Helm commands, use `helm help` or type a command followed by the `-h` flag: ```console $ helm get -h ``` | https://github.com/helm/helm-www/blob/main/docs/intro/quickstart.md | main | helm | [
0.08228066563606262,
0.09983985871076584,
-0.0326780341565609,
-0.04302404448390007,
0.07720780372619629,
0.010744770988821983,
-0.00009195016173180193,
0.032406099140644073,
0.01717454381287098,
0.013088405132293701,
0.04155947268009186,
-0.08474308252334595,
-0.031027022749185562,
-0.033... | -0.038003 |
This part of the Best Practices Guide focuses on templates. ## Structure of `templates/` The `templates/` directory should be structured as follows: - Template files should have the extension `.yaml` if they produce YAML output. The extension `.tpl` may be used for template files that produce no formatted content. - Te... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/templates.md | main | helm | [
-0.043443463742733,
0.04709970951080322,
0.029723888263106346,
-0.016898300498723984,
0.0320332832634449,
-0.0030337017960846424,
-0.013887596316635609,
0.03001413866877556,
0.007720820140093565,
0.021329281851649284,
0.022752288728952408,
0.0005042118136771023,
-0.022744031623005867,
0.03... | 0.027461 |
of adding `#` YAML comments on template sections containing Helm values that may be required by certain template functions. For example, if `required` function is introduced to the above example, and `maxMem` is unset, then a `#` YAML comment will introduce a rendering error. Correct: `helm template` does not render th... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/templates.md | main | helm | [
-0.04389666020870209,
0.0510038398206234,
0.06676016747951508,
0.03842337056994438,
0.05273282900452614,
-0.01800748147070408,
-0.04514498636126518,
0.02909691631793976,
0.024761969223618507,
0.01442645862698555,
-0.0016856846632435918,
0.0022176357451826334,
0.025704793632030487,
-0.00571... | 0.005755 |
This part of the Best Practices Guide explains general conventions. ## Chart Names Chart names must be lower case letters and numbers. Words \_may\_ be separated with dashes (-): Examples: ``` drupal nginx-lego aws-cluster-autoscaler ``` Neither uppercase letters nor underscores can be used in chart names. Dots should ... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/conventions.md | main | helm | [
0.0030759861692786217,
0.04583313316106796,
0.08004043251276016,
-0.050323840230703354,
0.02709709107875824,
-0.0024644958321005106,
-0.025636231526732445,
0.0028696225490421057,
0.0609087236225605,
0.01818469539284706,
0.03192353621125221,
-0.04547524079680443,
0.010038322769105434,
-0.03... | 0.067902 |
This section of the Best Practices Guide deals with creating and using Custom Resource Definition objects. When working with Custom Resource Definitions (CRDs), it is important to distinguish two different pieces: - There is a declaration of a CRD. This is the YAML file that has the kind `CustomResourceDefinition` - Th... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/custom_resource_definitions.md | main | helm | [
-0.037634268403053284,
0.02736932598054409,
0.054796747863292694,
-0.04218379035592079,
-0.00429950375109911,
0.002433347748592496,
-0.015916230157017708,
-0.006464766804128885,
0.14543980360031128,
0.01862075738608837,
-0.011587701737880707,
-0.03743840754032135,
0.011649778112769127,
-0.... | 0.075779 |
more useful for cluster operators who have admin access to a cluster | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/custom_resource_definitions.md | main | helm | [
0.0018718722276389599,
-0.0009257983765564859,
-0.03403153270483017,
0.015071477741003036,
-0.04764113202691078,
-0.023851415142416954,
0.05893728882074356,
-0.04227073863148689,
-0.056776516139507294,
0.013863813132047653,
-0.002984630176797509,
-0.01998363994061947,
-0.004236212931573391,
... | 0.204227 |
This part of the Best Practices Guide discusses formatting the Pod and PodTemplate portions in chart manifests. The following (non-exhaustive) list of resources use PodTemplates: - Deployment - ReplicationController - ReplicaSet - DaemonSet - StatefulSet ## Images A container image should use a fixed tag or the SHA of ... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/pods.md | main | helm | [
0.02379487082362175,
0.03863820433616638,
0.04008729010820389,
0.0052765002474188805,
0.036688726395368576,
0.0052325730212032795,
-0.011282828636467457,
0.027842268347740173,
0.03143814578652382,
0.04754345864057541,
0.021024204790592194,
-0.007918079383671284,
-0.007018555421382189,
-0.0... | 0.049006 |
This part of the best practices guide covers using values. In this part of the guide, we provide recommendations on how you should structure and use your values, with focus on designing a chart's `values.yaml` file. ## Naming Conventions Variable names should begin with a lowercase letter, and words should be separated... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/values.md | main | helm | [
0.009218594990670681,
0.05258296802639961,
0.03384982421994209,
-0.05580974370241165,
0.0029610558412969112,
0.0027133242692798376,
-0.029305171221494675,
0.026228532195091248,
0.05198309198021889,
0.024718645960092545,
0.012636667117476463,
-0.04078206047415733,
0.01453839149326086,
-0.03... | 0.011975 |
later time the order of the `servers` is changed. Easy to use: ```yaml servers: foo: port: 80 bar: port: 81 ``` Accessing foo's port is much more obvious: `--set servers.foo.port=80`. ## Document `values.yaml` Every defined property in `values.yaml` should be documented. The documentation string should begin with the n... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/values.md | main | helm | [
-0.012953406199812889,
0.00608457624912262,
0.013330100104212761,
-0.02001481130719185,
-0.06142733618617058,
-0.08654078841209412,
-0.005371674429625273,
-0.026457656174898148,
0.020371098071336746,
0.024869924411177635,
0.013541112653911114,
0.023076627403497696,
0.02458888292312622,
-0.... | 0.057534 |
This part of the Best Practices Guide discusses the best practices for using labels and annotations in your chart. ## Is it a Label or an Annotation? An item of metadata should be a label under the following conditions: - It is used by Kubernetes to identify this resource - It is useful to expose to operators for the p... | https://github.com/helm/helm-www/blob/main/docs/chart_best_practices/labels.md | main | helm | [
0.04153015464544296,
0.09798572957515717,
0.0361538864672184,
-0.04599105194211006,
0.035922907292842865,
0.06681569665670395,
0.02830001898109913,
0.015884727239608765,
0.08843007683753967,
0.034156836569309235,
-0.006902412045747042,
-0.08508644253015518,
-0.0017906425055116415,
-0.01938... | 0.09389 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.