Cilium gatewayAPI values for images seem to be missing for offline deploy

[bbaassssiiee]

When I set gatewayAPI: true and deploy offline, then the gateway pod is running OK in namespace envoy-gateway-system, but envoy is not.

envoy-gateway-system  envoy-default-eg-e41e7b31-7cff6b9565-9bxm4  ●  1/2   ImagePullBackOff 
envoy-gateway-system  envoy-gateway-6df5d94cb-mjxvr               ●  1/1   Running 

Could this values template be incomplete?

gatewayAPI:
  enabled: {{ cilium_gateway_api_enabled | to_json }}

https://github.com/kubernetes-sigs/kubespray/blob/422e7366ece34219bafedc33c542ea17514f5346/roles/network_plugin/cilium/templates/values.yaml.j2#L127C1-L128C54

https://gateway.envoyproxy.io/docs/tasks/operations/airgap-deployment/

[bbaassssiiee]

envoyproxy/gateway#5215

[bbaassssiiee]

Kubespray only installs the CustomResourceDefinitions. An actual gateway needs te be deployed another way.

apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
  name: custom-proxy-config
  namespace: system-gateway
spec:
  provider:
    type: Kubernetes
    kubernetes:
      envoyDeployment:
        container:
          image: "my-registry.examle.com/envoyproxy/envoy:distroless-v1.36.4

apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
metadata:
name: eg
spec:
controllerName: gateway.envoyproxy.io/gatewayclass-controller
parametersRef:
  group: gateway.envoyproxy.io
  kind: EnvoyProxy
  name: custom-proxy-config
  namespace: system-gateway

[vdveldet]

Envoy-gateway is an gateway API and cilium gateway can be installed as a gateway API.
That are 2 different things although they can be combined in one cluster.

I'm using envoy gateway installed from here -> https://gateway.envoyproxy.io/, without any "gatewayAPI" settings from kubespray.

For cilium_gateway_api_enabled to get this enabled from within kubespray you need some prereqs (most important: kubeProxyReplacement=true) but also:

gateway_api_enabled: true
cilium_gateway_api_enabled: true
cilium_kube_proxy_replacement: true

But then it will only work with "cluster" type, "nodeport" can not yet be configured in kubespray, some other settings can not be configured. (see also #12957)