helm: Add support for jamf_service to the teleport-kube-agent Helm chart

[lcharkiewicz]

This PR adds support for jamf_service configuration to the teleport-kube-agent Helm chart.

The change supports Jamf API Client Credentials auth method available in Teleport v16+

More about the required configuration can be found in the official Teleport docs.

Additional Jamf service options, like sync_period_* or filter_rsql can be configured by setting teleportConfig.

changelog: helm: add support for jamf_service to teleport-kube-agent

[rosstimothy]

For v16+ we should be pushing folks toward using client ID and client secret instead of username and password. cc @codingllama

[github-actions]

🤖 Vercel preview here: https://docs-m06cobads-goteleport.vercel.app/docs/ver/preview

[codingllama]

For v16+ we should be pushing folks toward using client ID and client secret instead of username and password. cc @codingllama

+1, please add fields for client ID and client secret, and document that these are preferred over username/password. All that is required already landed for v16 (see #41928 or public docs for reference).

[codingllama]

https://github.com/gravitational/teleport.e/issues/3765

[hugoShaka]

If we're going to ship this PR in v16, we can even remove the user/password fields so folks have to use client ID/secret.

[github-actions]

🤖 Vercel preview here: https://docs-3y9wt21dm-goteleport.vercel.app/docs/ver/preview

[lcharkiewicz]

If we're going to ship this PR in v16, we can even remove the user/password fields so folks have to use client ID/secret.

Currently both auth methods are supported. If keeping only Client Credentials is preferred, I'm happy to remove it.

[github-actions]

The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with changelog: followed by the changelog entries for the PR.

[rosstimothy]

If we're going to ship this PR in v16, we can even remove the user/password fields so folks have to use client ID/secret.

Currently both auth methods are supported. If keeping only Client Credentials is preferred, I'm happy to remove it.

@lcharkiewicz do we need this chart for any versions prior to v16? If no, then let's eliminate the user/password entirely and just ship the client credentials. That would simplify the chart a bit since the jamf client credentials are only supported on v16.

[github-actions]

🤖 Vercel preview here: https://docs-ioxcmqfsp-goteleport.vercel.app/docs/ver/preview

[github-actions]

🤖 Vercel preview here: https://docs-g1hd4tdsg-goteleport.vercel.app/docs/ver/preview

[lcharkiewicz]

If we're going to ship this PR in v16, we can even remove the user/password fields so folks have to use client ID/secret.

Currently both auth methods are supported. If keeping only Client Credentials is preferred, I'm happy to remove it.

@lcharkiewicz do we need this chart for any versions prior to v16? If no, then let's eliminate the user/password entirely and just ship the client credentials. That would simplify the chart a bit since the jamf client credentials are only supported on v16.

@rosstimothy I thought my team might need it with v15. After a discussion we decided that we can go with v16 only. Thus, I dropped the support for Jamf username and password auth (and yes, I like the simpler code now :)).

[lcharkiewicz]

@hugoShaka your suggestions have been addressed, PTAL.

[github-actions]

🤖 Vercel preview here: https://docs-730x5znld-goteleport.vercel.app/docs/ver/preview

[public-teleport-github-review-bot]

@lcharkiewicz See the table below for backport results.

Branch	Result
branch/v16	Create PR