Specify resources for ambassador-agent

[mskhor]

Is there an option to specify resources for ambassador-agent via helm values ?

spec: containers: - env: - name: LOG_LEVEL value: info - name: AGENT_NAMESPACE valueFrom: fieldRef: apiVersion: v1 fieldPath: metadata.namespace - name: AGENT_CONFIG_RESOURCE_NAME value: traffic-manager-ambassador-agent-cloud-token - name: RPC_CONNECTION_ADDRESS image: 'docker.io/ambassador/ambassador-agent:1.0.21' imagePullPolicy: IfNotPresent name: ambassador-agent ports: - containerPort: 8080 name: http protocol: TCP resources: {}

Only seeing below in helm values, but its not applied for ambassador-agent

agent: logLevel: resources: {} initResources: {} appProtocolStrategy: http2Probe port: 9900 image: registry: name: tag: pullSecrets: [] pullPolicy: IfNotPresent

[Alex Cantu]

Have you tried putting it under the ambassador-agent directive? For example, I use these values to disable the ambassador agent:

ambassador-agent:
  enabled: false

So maybe you're looking for something like:

ambassador-agent:
  resources:
    limits:
      cpu: 500m
      memory: 1Gi
    requests:
      cpu: 500m
      memory: 1Gi
   

[cindymullins-dw]

@mskhor , @alextricity25 , I believe the ambassador-agent for Telepresence is disabled by default. It's used to report your cluster to Ambassador so you could do things like have a service catalog.

As for the resource limits, would you want to adjust them for adherence to company policy perhaps? Is there another reason? This spec is not currently available so I don't think the above config example would work - this would probably be a feature request.

[Thomas Hallgren]

In the coming version 2.20.0, the ambassador-agent will be disabled by default. Please reopen this ticket if you still have an issue with it.