Importing gateway-proxy in ProxyTemplates manifest results in error

[marcoferrer]

What happened?

kuma versions

Client: Kuma 1.5.0
Server: Kuma 1.5.0

This documentation leads me to believe that when writing a ProxyTemplate for a new built in gateway I should import gateway-proxy

https://kuma.io/docs/dev/policies/proxy-template/#builtin-gateway-support

But doing so results in the following error message

The ProxyTemplate "edge-gateway" is invalid: spec.conf.imports[0]: profile not found. Available profiles: default-proxy

This can be reproduced by applying the following manifest

apiVersion: kuma.io/v1alpha1
kind: ProxyTemplate
mesh: default
metadata:
  name: edge-gateway
spec:
  selectors:
    - match:
        kuma.io/service: edge-gateway
  conf:
    imports:
      - gateway-proxy
    modifications:
      - cluster:
          operation: add
          value: |
            name: test-cluster
            connectTimeout: 5s
            type: STATIC

[marcoferrer]

It looks like the proxy template validator is initializing the available profiles map using a const that doesnt contain the new profile

kuma/pkg/core/resources/apis/mesh/proxytemplate_validator.go

Line 23 in 0dce9a4

for _, profile := range AvailableProfiles {

kuma/pkg/core/resources/apis/mesh/proxytemplate_profiles.go

Line 7 in 6c62248

var AvailableProfiles = []string{ProfileDefaultProxy}

kuma/pkg/plugins/runtime/gateway/plugin.go

Line 74 in d473989

const ProfileGatewayProxy = "gateway-proxy"

[github-actions]

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.