You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- The log-level parameters for controllers (including `fluxconfig-agent` and `fluxconfig-controller`) are now customizable. For more information, see [Configurable log-level parameters](tutorial-use-gitops-flux2.md#configurable-log-level-parameters).
138
+
- Helm chart changes to expose new SSH host key algorithm to connect to Azure DevOps. For more information, see [Azure DevOps SSH-RSA deprecation](tutorial-use-gitops-flux2.md#azure-devops-ssh-rsa-deprecation).
-The log-level parameters for controllers are now customizable. For more information, see [Configurable log-level parameters](tutorial-use-gitops-flux2.md#configurable-log-level-parameters).
-Improve the identity token generation logic to handle token generation failures
168
+
-The log-level parameters for controllers are now customizable. For more information, see [Configurable log-level parameters](tutorial-use-gitops-flux2.md#configurable-log-level-parameters).
168
169
169
170
## Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes
Copy file name to clipboardExpand all lines: articles/azure-arc/kubernetes/gitops-flux2-parameters.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "GitOps (Flux v2) supported parameters"
3
3
description: "Understand the supported parameters for GitOps (Flux v2) in Azure for use in Azure Arc-enabled Kubernetes and Azure Kubernetes Service (AKS) clusters."
4
-
ms.date: 02/08/2024
4
+
ms.date: 04/30/2024
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -55,15 +55,20 @@ For more information, see the [Flux documentation on Git repository checkout str
55
55
| ------------- | ------------- | ------------- |
56
56
|`--url``-u`|`http[s]://server/repo[.git]`| URL of the Git repository source to reconcile with the cluster. |
57
57
58
-
### Private Git repository with SSH and Flux-created keys
58
+
### Private Git repository with SSH
59
+
60
+
> [!IMPORTANT]
61
+
> Azure DevOps [announced the deprecation of SSH-RSA](https://aka.ms/ado-ssh-rsa-deprecation) as a supported encryption method for connecting to Azure repositories using SSH. If you use SSH keys to connect to Azure repositories in Flux configurations, we recommend moving to more secure RSA-SHA2-256 or RSA-SHA2-512 keys. For more information, see [Azure DevOps SSH-RSA deprecation](tutorial-use-gitops-flux2.md#azure-devops-ssh-rsa-deprecation).
62
+
63
+
#### Private Git repository with SSH and Flux-created keys
59
64
60
65
Add the public key generated by Flux to the user account in your Git service provider.
61
66
62
67
| Parameter | Format | Notes |
63
68
| ------------- | ------------- | ------------- |
64
69
|`--url``-u`|`ssh://user@server/repo[.git]`|`git@` should replace `user@` if the public key is associated with the repository instead of the user account. |
65
70
66
-
### Private Git repository with SSH and user-provided keys
71
+
####Private Git repository with SSH and user-provided keys
67
72
68
73
Use your own private key directly or from a file. The key must be in [PEM format](https://aka.ms/PEMformat) and end with a newline (`\n`).
69
74
@@ -75,7 +80,7 @@ Add the associated public key to the user account in your Git service provider.
75
80
|`--ssh-private-key`| Base64 key in [PEM format](https://aka.ms/PEMformat)| Provide the key directly. |
76
81
| `--ssh-private-key-file` | Full path to local file | Provide the full path to the local file that contains the PEM-format key.
77
82
78
-
### Private Git host with SSH and user-provided known hosts
83
+
####Private Git host with SSH and user-provided known hosts
79
84
80
85
The Flux operator maintains a list of common Git hosts in its `known_hosts` file. Flux uses this information to authenticate the Git repository before establishing the SSH connection. If you're using an uncommon Git repository or your own Git host, you can supply the host key so that Flux can identify your repository.
> Azure DevOps [announced the deprecation of SSH-RSA](https://aka.ms/ado-ssh-rsa-deprecation) as a supported encryption method for connecting to Azure repositories using SSH. If you use SSH keys to connect to Azure repositories in Flux configurations, we recommend moving to more secure RSA-SHA2-256 or RSA-SHA2-512 keys. For more information, see [Azure DevOps SSH-RSA deprecation](tutorial-use-gitops-flux2.md#azure-devops-ssh-rsa-deprecation).
168
+
161
169
For both cases, when you create the Flux configuration, use `--local-auth-ref my-custom-secret` in place of the other authentication parameters:
@@ -568,7 +568,7 @@ If you don't specify values for `memoryThreshold` and `outOfMemoryWatch`, the de
568
568
569
569
## Configurable log-level parameters
570
570
571
-
By default, the `log-level` for Flux controllers is set to `info`. Starting with [`microsoft.flux` v1.8.3](extensions-release.md#flux-gitops), you can modify these default settings using the `k8s-extension` command as follows:
571
+
By default, the `log-level` for Flux controllers is set to `info`. Starting with `microsoft.flux` v1.8.3, you can modify these default settings using the `k8s-extension` command as follows:
Valid values are `debug`, `info`, or `error`. These values are only configurable for the controllers listed above; they don't apply to the `fluxconfig-agent` and `fluxconfig-controller`.
583
-
584
-
For instance, to change the `log-level` for the `source-controller` and `kustomize-controller`, use the following command:
582
+
Valid values are `debug`, `info`, or `error`. For instance, to change the `log-level` for the `source-controller` and `kustomize-controller`, use the following command:
Starting with [`microsoft.flux` v1.9.1](extensions-release.md#flux-gitops), `fluxconfig-agent` and `fluxconfig-controller` support `info` and `error` log levels (but not `debug`). These can be modified by using the k8s-extension command as follows:
Azure DevOps [announced the deprecation of SSH-RSA](https://aka.ms/ado-ssh-rsa-deprecation) as a supported encryption method for connecting to Azure repositories using SSH. If you use SSH keys to connect to Azure repositories in Flux configurations, we recommend moving to more secure RSA-SHA2-256 or RSA-SHA2-512 keys.
604
+
605
+
When reconciling Flux configurations, you might see an error message indicating ssh-rsa is about to be deprecated or is unsupported. If so, update the host key algorithm used to establish SSH connections to Azure DevOps repositories from the Flux `source-controller` and `image-automation-controller` (if enabled) by using the `az k8s-extension update` command. For example:
For more information on Azure DevOps SSH-RSA deprecation, see [End of SSH-RSA support for Azure Repos](https://aka.ms/ado-ssh-rsa-deprecation).
614
+
590
615
### Workload identity in AKS clusters
591
616
592
617
Starting with [`microsoft.flux` v1.8.0](extensions-release.md#flux-gitops), you can create Flux configurations in [AKS clusters with workload identity enabled](/azure/aks/workload-identity-deploy-cluster). To do so, modify the flux extension as shown in the following steps.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments