v0.2.4

Fixed

• Disable logger development mode to avoid panicking, use zap as logger.

v0.2.3

Release v0.2.3 (#89)

v0.2.2

Release v0.2.2 (#67)

v0.2.1

Added

• Add toleration for node.cluster.x-k8s.io/uninitialized taint.
• Add node affinity to prefer schedule to control-plane nodes.

v0.2.0

Added

• Add a new feature that injects private endpoint to workload clusters for WC-to-MC ingress communication for private MCs.

v0.1.1

Changed

• Configure gsoci.azurecr.io as the default container image registry.
• Add toggle for PSPs.

v0.1.0

Fixed

• Add required values for pss policies.

Added

• Add privatelinks package with Scope object that is providing functionality to access and update private links info in AzureCluster CR.
• Add custom Makefile
• Add CircleCI config
• Add this changelog
• Add Helm chart
• Add privateendpoints package with scope object that is providing functionality to access and update private endpoints in AzureCluster CR.
• Add private endpoints reconciler Service
• Add AzureCluster controller

Changed

• Updated Dockerfile

v0.1.0-alpha.13

Working alpha release that has been pushed to capz-app-collection.

High overview of the features:

• Reconciles AzureCluster CRs for workload clusters with private network mode.
  • It expects that private WC API server is exposed via Azure Private Link.
• For every private workload cluster it ensures that a private endpoint is added to the MC AzureCluster CR.
  • It just adds the private endpoint entry in the MC AzureCluster CR, then CAPZ creates the private endpoint.
• For every private workload cluster, after the private endpoint has been created, it sets private endpoint private IP address in the azure-private-endpoint-operator.giantswarm.io/private-link-apiserver-ip annotation in WC AzureCluster CR.
  • dns-operator-azure will then use this annotation to create required A record in the private DNS zone linked to MC VNet.
• With the above setup, MC apps (e.g. CAPI and CAPZ) can access WC API server via DNS name apiserver.<WC BASE DOMAIN>.
  • e.g. apiserver.myprivatecluster.azuretest.gigantic.io

After additional testing a beta release will be published.