-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable GitOps config as an AKS add-on #1967
Comments
Hi seanmck, AKS bot here 👋 I might be just a bot, but I'm told my suggestions are normally quite good, as such:
|
How would this affect AKS clusters that use Flux (v1 or V2) ? We have deployed Flux in its own namespace. If this is available as an update to an existing cluster than all it takes is to remove the current deployment and enable the managed Flux. |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
how often would the gitops toolkit being used be updated? I am interested in knowing the support lifecycle policy of updating these with upstream versions of the gitops tool (flux argo CD etc) |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
Is there any update for this feature or ETA? |
This feature is described as available in the Azure Arc documentation and Azure Policy, but Edit: connected the cluster to Arc successfully |
@Azure/aks-pm issue needs labels |
12 similar comments
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
@Azure/aks-pm issue needs labels |
Is there an ETA update on this feature? 🙏 |
I'm keen to know this as well. A bit concerning there's been no update for a while. Nothing stopping you from enabling it now, but would be good to know if that's advised or not at this time |
I had attempted to add feature but sadly not available in UKSouth 🥲 |
Ah right ok, i was using it in West Europe. This is a good article to read if you haven't already https://pixelrobots.co.uk/2021/07/first-look-gitops-on-azure-kubernetes-service-using-the-aks-addon-preview/ |
The official docs can be found at https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/tutorial-use-gitops-flux2. For some reason they are under arc and not AKS which is a bit confusing for customers. Would be good to separate them out. |
Agree with this |
Will GitOps be enabled as an add-on rather than an extension? Automatically installing as an add-on enables some enterprise-style deployment flows which we otherwise can't have if we need to install the extension e.g. using Azure Policy to DINE a |
From what I know the AKS addon for GitOps is no longer a thing. It was just for flux v1. The extension is the new and only way to install it as it needs to integrate with ARM and addons cannot do that. |
Yeah I understand this to be true for v1
Is that true? Add-ons like Azure Policy or OMS Agent are defined in the body of a request for So to my knowledge, the opposite of what you wrote is true; add-ons are integrated with ARM and extensions are not. No? Happy to be enlightened if I've misunderstood :) |
@rossdotpink resource fluxExtension 'Microsoft.KubernetesConfiguration/extensions@2021-09-01' = {
scope: aksCluster
name: 'flux'
properties: {
extensionType: 'Microsoft.Flux'
... # Omitted for brevity
}
} There is limited documentation available on how to configure this. However, I got a lot from looking at how it is implemented in the AKS Secure Baseline. |
Hi, sorry for the confusion. When I say integrated with ARM I am not meaning ARM templates or Bicep. Extensions can be installed via ARM and Bicep as @Agger1995 has shown above. What I was referring to can be read about in the docs. https://docs.microsoft.com/en-us/azure/aks/integrations#extensions "Cluster extensions build on top of certain Helm charts and provide an Azure Resource Manager-driven experience for installation and lifecycle management of different Azure capabilities on top of your Kubernetes cluster." This allows for the GitOps section to show in the Azure portal from what I understand. Hope that clears some stuff up for you. |
@Agger1995 Thanks! I did not know I could do that, I will give that a go. Totally agree about the documentation, but it's getting better :) @PixelRobots Thanks :) main point I was missing is that extensions can indeed be installed as part of ARM/Bicep request, rather than just AZ CLI. Also, thank you for the Pixel Robots website; I knew I recognised it from somewhere, some of the first material I found on GitOps Flux on AKS was on your website. |
Any time. glad it helped. AKS addons and AKS Cluster Extensions can get a bit confusing especially when it comes to updating them. Check out my blog post on that to ensure you keep your clusters updated. https://pixelrobots.co.uk/2022/02/azure-kubernetes-service-aks-addons-and-extensions-who-is-responsible/ |
When will this be available in Norwayeast? |
This issue tracks enabling of GitOps config as an AKS add-on. This add-on will make it easy for AKS clusters to participate in GitOps-based deployments alongside Azure Arc-connected clusters:
https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/use-gitops-connected-cluster
The text was updated successfully, but these errors were encountered: