Patryk Małek

ARM64 support: some of the images used in docs don't run on arm64

7

### Where is the problem? https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/using-gateway-api/#set-up-an-echo-server ### What happened? When following the guide on https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/using-gateway-api/#set-up-an-echo-server I deployed https://bit.ly/echo-service manifest (https://gist.github.com/hbagdi/0d833181239a39172ba70cbec080bdb9) which deploys `gcr.io/kubernetes-e2e-test-images/echoserver:2.2`. This images does not run on arm64....

Allow multiple `ingress` releases with the same name but in different namespaces

4

### Problem statement Currently, `ingress` (through the means of `kong` subcharts) chart [creates a `ClusterRole`](https://github.com/Kong/charts/blob/72650f5768dde1867812fab42e863de7db60f80f/charts/kong/templates/controller-rbac-resources.yaml#L92-L97) named https://github.com/Kong/charts/blob/d65e5d1ed44c29bf1ecf896edb056a19614661af/charts/kong/templates/_helpers.tpl#L20 which (when `.Values.nameOverride` is unspecified) collides since it uses the same name `default...

ingress: enforce expressions router flavor when using KIC v3.0+

1

#### What this PR does / why we need it: Use an obscure `.Subcharts` variable to get subcharts values and based on that enforce the `expressions` router flavor in Kong...

TLS with user provided secret doesn't seem to work

4

### Problem statement While trying to make mTLS between KIC and Admin API work I encountered some difficulties so I thought I'd share some of them. Using the following script...

### Problem statement When using `kong` chart, users cannot install more than 1 ingress controller releases with the same name in different namespaces. ``` $ helm upgrade --install --create-namespace -n...

### Problem statement Kubernetes introduced (bet and disabled by default in 1.28) `ValidatingAdmissionPolicy` which can be used to offload some of the work done by validating admission webhook. This issue...

### Problem statement `kong` chart's `Pod`s are deployed with a set of labels, among those there is `app.kubernetes.io/version`, which has its value always set to [`.Chart.AppVersion`](https://github.com/Kong/charts/blob/d65e5d1ed44c29bf1ecf896edb056a19614661af/charts/kong/templates/_helpers.tpl#L33). This is incorrect because...

As of now (2.16) we still have the pin on postgres image in: https://github.com/Kong/charts/blob/1c5242fd3a7375c61f005d88d757fa37ed5c02aa/charts/kong/values.yaml#L598-L600 Given that https://github.com/Kong/kong/issues/8533 is resolved, we should be able to remove that pinned tag. I've done...

Migrate from `PodSecurityPolicy` to the Built-In PodSecurity Admission Controller to support k8s 1.25+

2

Kubernetes 1.25 removes support for `PodSecurityPolicy`: https://kubernetes.io/blog/2022/08/23/kubernetes-v1-25-release/#pod-security-changes which we currently use in kong chart. In order to support versions 1.25 and higher we should migrate to use PodSecurity Admission Controller...

As per title:  Example where this failed: https://github.com/Kong/charts/pull/645