WARP Client, Private Network access & K8 Container

Hi there,

cloudflared has been successfully deployed as a container in a kubernetes cluster

Private resources outside of the K8 cluster is accessible over cloudflared tunnel and works beautifully.

Part of the kube deployment.yaml is

    spec:
      containers:
        - name: cloudflared
          image: xxxxxxxxxx
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 40355
              name: http
              protocol: TCP
          args:
          - tunnel
          - --config
          - /etc/cloudflared/config/config.yaml
          - --metrics
          - 0.0.0.0:40355
          - run
          volumeMounts:
          - name: config
            mountPath: /etc/cloudflared/config
            readOnly: true

and config.yaml is :

# Name of the tunnel you want to run
tunnel: cf-zt-tunnel-lab
loglevel: debug
protocol: http2
tracetransport-loglevel: warn
credentials-file: /etc/cloudflared/<redacted>.json
metrics: 0.0.0.0:2000
no-autoupdate: true
warp-routing:
  enabled: true
ingress:
- hostname: sap.example.com
  service: https://10.1.100.36
  originRequest:
    connectTimeout: 10s
    noTLSVerify: true
- hostname: internalapp.example.com
  service: https://10.10.100.3
  originRequest:
    connectTimeout: 10s
    noTLSVerify: true
- service: http_status:404

Now want to enable private network access via WARP client.
While following https://developers.cloudflare.com/cloudflare-one/tutorials/warp-to-tunnel , I have to run the following command, prior to start the cloudflared

cloudflared tunnel route ip add 10.100.1.0/24 <tunnel-id>

But how to incorporate this route ip add command within kubernetes deployment mentioned above.

Any hints or tips highly appreciate.

Thank you,
mS