v0.5.26 Armory Agent Service (2021-09-10)
New features and improvements
You can now control the Armory Agent’s behavior when a failed request to the Kubernetes API server occurs:
kubernetes: retries: enabled: true # (Optional, boolean, default: true). Enable or disable retries when the Armory Agent makes a failed request to the Kubernetes API server. maxRetries: 3 # (Optional, integer, default: 3): The number of times that the Armory Agent will try the same request if it fails. backOffMs: 3000 # (Optional, integer, default: 3000): How much time (in milliseconds) to wait between retry attempts. retryAnyError: false # (Optional, boolean, default: false): Optional. If true, Agent will retry when encountering any error from the Kubernetes API server. If false, Agent will only retry if the error contains any item from `retryableErrors.` retryableErrors: # (Optional, list of strings, default: "timeout", "deadline exceeded"): Optional. If the error from the Kubernetes API server contains any item from this list, the request will be retried. Requires `retryAnyError` to be `false`. - "timeout" - "deadline exceeded"
Kubernetes account permissions format
kubernetes: accounts: - name: my-k8s-account permissions: - READ: ['role1', 'role2'] - WRITE: ['role3', 'role4']
Make sure that there are no whitespaces in the role configurations under the
WRITE tags. The permissions are not applied if there are whitespaces in the configuration. This means that all users will have access to the defined account.
Affected versions: all versions
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified March 3, 2023: (2d069084)